svn commit: r470670 - in /maven/site/trunk: notes.txt profile-example.txt src/site/xdoc/docs-required.xml

[br...@apache.org]

Author: brett
Date: Thu Nov  2 20:45:07 2006
New Revision: 470670

URL: http://svn.apache.org/viewvc?view=rev&rev=470670
Log:
consolidate the 'required docs' page

Removed:
    maven/site/trunk/notes.txt
    maven/site/trunk/profile-example.txt
Modified:
    maven/site/trunk/src/site/xdoc/docs-required.xml

Modified: maven/site/trunk/src/site/xdoc/docs-required.xml
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/xdoc/docs-required.xml?view=diff&rev=470670&r1=470669&r2=470670
==============================================================================
--- maven/site/trunk/src/site/xdoc/docs-required.xml (original)
+++ maven/site/trunk/src/site/xdoc/docs-required.xml Thu Nov  2 20:45:07 2006
@@ -59,7 +59,112 @@
         <li>Intro to Plexus</li>
         <li>contributors guide (add to current and consolidate, walk through some first steps)</li>
       </ul>
+      <h4>Additional Notes</h4>
+      <pre>
+        Brett Porter wrote:
+        > The active project changes during the reactor build. At the compile
+        > stage, it refers to the target/classes directory. At the package
+        > stage, it points to the jar file. If you are implementing your own
+        > packaging goal, you need to call project.getArtifact().setFile( ... )
+        > to ensure this is used.
+
+        - multi module howto
+        - per user scm setup
+          - outline behaviour when connection and developConnection are defined
+
+           Our current URL looks like:
+           scm:cvs:pserver:@cvs.host.name:/cvsroot:module-version
+
+           Using this URL, the default is to connect to the CVS server using the
+           same userid as the current user.  This is the desired behavior and I
+           don't want to mess that up.  I just would like a means to add a userid
+           in the URL only in special circumstances like Continuum.
+
+           We might want to do something where we say it is a best practice to
+           specify a ${user} and take it from the environment and allow an override.
+
+        - testing a plugin
+        - How to get started behind an NTLM proxy.
+        - How snapshots works
+        - How do i use the lifecycle provided by a plugin:
+        - How do i disable ibiblio
+        - using version ranges
+        - plugin expressions (look at bob allison's work)
+        - overriding the central repository (use central)
+        - description of what packagings are available and how they work
+        - creating upload bundles
+        - modello example
+        - changing the snapshot policy frequency
+        - overriding central repo
+        - using POM info in applications: the POM is packaged so there is acccess
+          continuum example to get the version.
+        - quick description of scm,wagon,continuum        
+      </pre>
+      <h4>Profiles Example</h4>
+      <pre><![CDATA[
+it's possible to do it with m2 beta-1 and profiles.
+
+you declare profile in your pom like this :
+
+   <profiles>
+     <profile>
+       <id>env-test</id>
+       <activation>
+         <property>
+           <name>env</name>
+           <value>test</value>
+         </property>
+       </activation>
+       <properties>
+         <appProperties>test.properties</appProperties>
+       </properties>
+     </profile>
+     <profile>
+       <id>env-production</id>
+       <activation>
+         <property>
+           <name>env</name>
+           <value>production</value>
+         </property>
+       </activation>
+       <properties>
+         <appProperties>app.properties</appProperties>
+       </properties>
+     </profile>
+   </profiles>
+
+and you can run mvn with one of profiles like :
+mvn -P env-production clean:clean install ==> we use the profile id
+or
+mvn -Denv=test clean:clean install ==> we use the property env define in
+<activation>
+
+Emmanuel
+
+martin.kuhn@merkur.at wrote:
+> Hi,
+>
+> I'm a maven newbie and I try out maven 2.0 alpha 3.
+>
+> My questions:
+>
+> I have a project to build / deploy for three different enviroments (test,
+> integration, production).
+>
+> The difference beetween the bundles is only a properties file (there are
+> three different files: config-test.properties,
+> config-integration.properties ...).
+> In the build process I want to copy the right config file to a file with a
+> common name (config.properties -> the app should work with this config
+> file)
+>
+> Is there a solution to handle this with maven 2 or do I have to write a
+> plugin?
+>
+        ]]>
+      </pre>
     </section>
   </body>
 </document>
+