Index: src/site/apt/guides/index.apt
===================================================================
--- src/site/apt/guides/index.apt	(revision 549731)
+++ src/site/apt/guides/index.apt	(working copy)
@@ -111,6 +111,9 @@
  * {{{mini/guide-webapp.html}Webapps}}
 
  * {{{mini/guide-using-extensions.html}Using Extensions}}
+ 
+ * {{{mini/guide-building-for-different-environments.html}Building For Different Environments with Maven 2}}
+ 
 
 ** Testing
 
Index: src/site/apt/guides/mini/guide-building-for-different-environments.apt
===================================================================
--- src/site/apt/guides/mini/guide-building-for-different-environments.apt	(revision 0)
+++ src/site/apt/guides/mini/guide-building-for-different-environments.apt	(revision 0)
@@ -0,0 +1,148 @@
+ ---
+ Building For Different Environments with Maven 2
+ ---
+ 01-Jan-2006
+ ---
+ Trygve Laugstøl
+ ---
+
+Building For Different Environments with Maven 2
+
+  Building the same artifact for different environments has always been an annoyance. You have multiple environments,
+     for instance test and production servers or, maybe a set of servers that run the same application with different
+     configurations. In this guide I'll explain how you can use profiles to build and package artifacts configured for
+     specific environments. See {{{../introduction/introduction-to-profiles.html}Introduction to Build Profiles}} for a
+     more in-depth explanation of the profile concept.
+  
+  Note:
+  
+  * This guide assume that you have basic Maven 2 knowledge.
+  
+  * It will show a way to configure Maven to solve simple configuration set-ups only. By simple configuration set-up I
+     mean cases where you only have a single file or a small set of files that vary for each environment. There are
+     other and better ways to handle two and many-dimensional configuration issues.
+  
+  
+  This example assume the use of the
+     {{{../introduction/introduction-to-the-standard-directory-layout.html}Standard Directory Layout}}. A fully-working
+     example project can be found {{{http://www.codehaus.org/~trygvis/static/2006/simpleenvironment.tar.gz} here}}.
+  
+----
+pom.xml
+src/
+  main/
+    java/
+    resources/
+  test/
+    java/
+----
+
+
+ Under <<<src/main/resources>>>  there are three files:
+ 
+ * <<<environment.properties>>>  - This is the default configuration and will be packaged in the artifact by default.
+ 
+ * <<<environment.test.properties>>> - This is the variant for the test environment.
+ 
+ * <<<environment.prod.properties>>> - This is basically the same as the test variant and will be used in the
+   production environment.
+
+ In the project descriptor, you need to configure the different profiles. Only the test profile is showed here, see the
+   {{{http://www.codehaus.org/~trygvis/static/2006/simpleenvironment.tar.gz} accompanying source code}} for the full
+   pom.xml.
+
+----
+ <profiles>
+   <profile>
+     <id>test</id>
+     <build>
+       <plugins>
+         <plugin>
+           <artifactId>maven-antrun-plugin</artifactId>
+           <executions>
+             <execution>
+               <phase>test</phase>
+               <goals>
+                 <goal>run</goal>
+               </goals>
+               <configuration>
+                 <tasks>
+                   <delete file="${project.build.outputDirectory}/environment.properties"/>
+                   <copy file="src/main/resources/environment.test.properties"
+                         tofile="${project.build.outputDirectory}/environment.properties"/>
+                 </tasks>
+               </configuration>
+             </execution>
+           </executions>
+         </plugin>
+         <plugin>
+           <artifactId>maven-surefire-plugin</artifactId>
+           <configuration>
+             <skip>true</skip>
+           </configuration>
+         </plugin>
+         <plugin>
+           <artifactId>maven-jar-plugin</artifactId>
+           <executions>
+             <execution>
+               <phase>package</phase>
+               <goals>
+                 <goal>jar</goal>
+               </goals>
+               <configuration>
+                 <classifier>test</classifier>
+               </configuration>
+             </execution>
+           </executions>
+         </plugin>
+       </plugins>
+     </build>
+   </profile>
+
+   .. Other profiles goes here ..
+
+ </profiles>
+----
+
+ Three things are configured in this snippet:
+
+ [[1]] It configures the antrun plugin to execute the run goal in the test phase where it will copy the
+   <<<environment.test.properties>>> file to <<<environment.properties>>>.
+
+ [[2]] It will configure the test plugin to skip all tests when building the test and production artifacts.
+   This is useful as you probably don't want to run tests against the production system
+
+ [[3]] It configures the JAR plugin to create an "attached" JAR with the "test" classifier.
+
+ To activate this profile execute <<<mvn -Ptest install>>>  and maven will execute the steps in the profile
+   in addition to the normal steps. From this build you will get two artifacts, "foo-1.0.jar" and "foo-1.0-test.jar".
+   These two jars will identical.  
+
+Caveats
+
+   * Currently Maven 2 doesn't allow a project build to only produce attached artifacts. (i.e. it has to produce a
+   "main" artifact as well) This results in two equal JARs beeing packaged and installed. The JAR plugin probably
+   should also get improved support for this use case to that two different output directories will be used as the
+   basis for building the JAR.
+
+   * The usage of the delete task might seem a bit odd but is required to make sure that the copy task actually will
+   copy the file. The copy task will look at the timestamps of the source and destination files, only when copying the
+   files it won't know that the actualy source file might be different than the last time it was executed.
+
+   * After the build the test configuration will be in target/classes and won't be overridden because the resources
+   plugin uses the same timestamp checking, so you should always do a clean after executing Maven with a profile.
+
+   * For the reasons given above it's imperative that you only build an artifact for a single environment in a single
+   execution at a time and that you execute "mvn clean" whenever you change the profile switches. If not, you might get
+   artifacts with a mixed set of configuration files.
+
+Resources
+
+   [[1]] {{{../introduction/introduction-to-profiles.html}Introduction to Build Profiles}}
+
+   [[2]] {{{../introduction/introduction-to-the-standard-directory-layout.html}Standard Directory Layout}}
+
+   [[3]] {{{http://www.codehaus.org/~trygvis/static/2006/simpleenvironment.tar.gz} The accompanying source code}}
+
+ ~~{{{http://blogs.codehaus.org/mt-tb.cgi?__mode=view&entry_id=1296}TrackBack}}
+