If I have, for example, a property defined in my maven settings.xml as follows:
<settings>
<profiles>
<profile>
<id>compile</id>
<properties>
<JAVA_1_3_HOME>C:\j\jdk1.3.1_18</JAVA_1_3_HOME>
<JAVA_1_4_HOME>C:\j\jdk1.4.2_19</JAVA_1_4_HOME>
<JAVA_1_5_HOME>C:\j\jdk1.5.0_01</JAVA_1_5_HOME>
<JAVA_1_6_HOME>C:\j\jdk1.6.0_17</JAVA_1_6_HOME>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>v</activeProfile>
</activeProfiles>
</settings>
Then the bundle-plugin will output those properties to the jar's
MANIFEST.MF file...
<snip>
Manifest-Version: 1.0
Export-Package: ....
JAVA_1_4_HOME: C:\j\jdk1.4.2_19
JAVA_1_6_HOME: C:\j\jdk1.6.0_17
JAVA_1_5_HOME: C:\j\jdk1.5.0_01
Tool: Bnd-0.0.238
Bundle-Name: Commons IO
Created-By: 1.6.0_17 (Sun Microsystems Inc.)
JAVA_1_3_HOME: C:\j\jdk1.3.1_18
...
</snip>
Is there a way to avoid this?
Thanks
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
