Author: niallp
Date: Sat Mar 13 12:41:04 2010
New Revision: 922546
URL: http://svn.apache.org/viewvc?rev=922546&view=rev
Log:
Add note about maven-bundle-plugin and add example settings.xml
Modified:
commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
Modified: commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
URL:
http://svn.apache.org/viewvc/commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml?rev=922546&r1=922545&r2=922546&view=diff
==============================================================================
--- commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml (original)
+++ commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml Sat Mar 13
12:41:04 2010
@@ -247,20 +247,46 @@
<p>
In order for these profiles to work, you need to configure the
<code>JAVA_1_3_HOME</code>,
<code>JAVA_1_4_HOME</code>, <code>JAVA_1_5_HOME</code> and
<code>JAVA_1_6_HOME</code>
- properties in your <code>settings.xml</code> file (or as environment
variables or even command-line properties). See
- <a
href="http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html";>here</a>
for details.
- There is no need to configure all the properties.
- Each property should be set to the <code>directory</code> where the
relevant version of the JDK is installed.
- For example on a Windows system the values might be:
+ properties in your <code>settings.xml</code> file (or as environment
variables or even command-line properties).
+ See <a
href="http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html";>here</a>
+ for details. Each property should be set to the
<code>directory</code> where the relevant version of the JDK is installed.
</p>
- <source>
- <properties>
- <JAVA_1_3_HOME>C:\jdk1.3.1_20</JAVA_1_3_HOME>
- <JAVA_1_4_HOME>C:\j2sdk1.4.2_19</JAVA_1_4_HOME>
- <JAVA_1_5_HOME>C:\jdk1.5.0_22</JAVA_1_5_HOME>
- <JAVA_1_6_HOME>C:\jdk1.6.0_18</JAVA_1_6_HOME>
- </properties>
- </source>
+ <p>
+ Unfortunately the <a
href="http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html";>maven-bundle-plugin</a>
+ will output these property values to the jar's
<code>MANIFEST.MF</code> file. You can avoid this
+ by defining the property in the profile its used in in your
<code>settings.xml</code>, for example:
+
+ </p>
+ <source><![CDATA[
+ <settings>
+ <profiles>
+ <profile>
+ <id>java-1.3</id>
+ <properties>
+ <JAVA_1_3_HOME>C:\j\jdk1.3.1_18</JAVA_1_3_HOME>
+ </properties>
+ </profile>
+ <profile>
+ <id>java-1.4</id>
+ <properties>
+ <JAVA_1_4_HOME>C:\j\jdk1.4.2_19</JAVA_1_4_HOME>
+ </properties>
+ </profile>
+ <profile>
+ <id>java-1.5</id>
+ <properties>
+ <JAVA_1_5_HOME>C:\j\jdk1.5.0_01</JAVA_1_5_HOME>
+ </properties>
+ </profile>
+ <profile>
+ <id>java-1.6</id>
+ <properties>
+ <JAVA_1_6_HOME>C:\j\jdk1.6.0_17</JAVA_1_6_HOME>
+ </properties>
+ </profile>
+ </profiles>
+ </settings>
+ ]]></source>
<p>
(Since the values only depend on the location of the Java
installations on your local machine,
and will probably not change frequently, using the
<code>settings.xml</code> file is generally
