You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thorsten Möller (JIRA)" <ji...@codehaus.org> on 2010/10/10 21:05:32 UTC
[jira] Created: (MSHARED-166) Merging with existing MANIFEST.MF
looses Class-Path element
Merging with existing MANIFEST.MF looses Class-Path element
-----------------------------------------------------------
Key: MSHARED-166
URL: http://jira.codehaus.org/browse/MSHARED-166
Project: Maven Shared Components
Issue Type: Bug
Components: maven-archiver
Affects Versions: maven-archiver-2.4.1
Reporter: Thorsten Möller
Attachments: MANIFEST.MF_final_with_maven-bundle-plugin, MANIFEST.MF_final_without_maven-bundle-plugin, MANIFEST.MF_maven-bundle-plugin
I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data). The plugin configuration is as follows (excerpt from effective POM):
{code:xml}
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.1.0</version>
<extensions>true</extensions>
<executions>
<execution>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
<configuration>
<instructions>
<Export-Package>org.mindswap.*</Export-Package>
<Private-Package>impl.*</Private-Package>
<RequiredExecutionEnvironment>J2SE-1.5</RequiredExecutionEnvironment>
</instructions>
</configuration>
</plugin>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<archive>
<manifestFile>/Users/thorsten/development/on/owls-api/target/classes/META-INF/MANIFEST.MF</manifestFile>
<compress>true</compress>
<manifest>
<addClasspath>false</addClasspath>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
</manifest>
</archive>
</configuration>
</plugin>
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-166) Merging with existing MANIFEST.MF
looses Class-Path element
Posted by "Thorsten Möller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238318#action_238318 ]
Thorsten Möller commented on MSHARED-166:
-----------------------------------------
The first two sentences might be confusing. Should be:
I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data for the MANIFEST.MF file). In short, the bundle plugin creates a MANIFEST.MF(_maven-bundle-plugin) file containing all OSGi related meta data.
> Merging with existing MANIFEST.MF looses Class-Path element
> -----------------------------------------------------------
>
> Key: MSHARED-166
> URL: http://jira.codehaus.org/browse/MSHARED-166
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Reporter: Thorsten Möller
> Attachments: MANIFEST.MF_final_with_maven-bundle-plugin, MANIFEST.MF_final_without_maven-bundle-plugin, MANIFEST.MF_maven-bundle-plugin
>
>
> I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data). The plugin configuration is as follows (excerpt from effective POM):
> {code:xml}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <version>2.1.0</version>
> <extensions>true</extensions>
> <executions>
> <execution>
> <goals>
> <goal>manifest</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <instructions>
> <Export-Package>org.mindswap.*</Export-Package>
> <Private-Package>impl.*</Private-Package>
> <RequiredExecutionEnvironment>J2SE-1.5</RequiredExecutionEnvironment>
> </instructions>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.3.1</version>
> <configuration>
> <archive>
> <manifestFile>/Users/thorsten/development/on/owls-api/target/classes/META-INF/MANIFEST.MF</manifestFile>
> <compress>true</compress>
> <manifest>
> <addClasspath>false</addClasspath>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> </archive>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSHARED-166) Merging with existing MANIFEST.MF
looses Class-Path element
Posted by "Thorsten Möller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thorsten Möller closed MSHARED-166.
-----------------------------------
Resolution: Not A Bug
It was actually a bug in my POM. I had two plugin sections for the maven-jar-plugin.
Sorry for the noise.
> Merging with existing MANIFEST.MF looses Class-Path element
> -----------------------------------------------------------
>
> Key: MSHARED-166
> URL: http://jira.codehaus.org/browse/MSHARED-166
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Reporter: Thorsten Möller
> Attachments: MANIFEST.MF_final_with_maven-bundle-plugin, MANIFEST.MF_final_without_maven-bundle-plugin, MANIFEST.MF_maven-bundle-plugin
>
>
> I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data). The plugin configuration is as follows (excerpt from effective POM):
> {code:xml}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <version>2.1.0</version>
> <extensions>true</extensions>
> <executions>
> <execution>
> <goals>
> <goal>manifest</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <instructions>
> <Export-Package>org.mindswap.*</Export-Package>
> <Private-Package>impl.*</Private-Package>
> <RequiredExecutionEnvironment>J2SE-1.5</RequiredExecutionEnvironment>
> </instructions>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.3.1</version>
> <configuration>
> <archive>
> <manifestFile>/Users/thorsten/development/on/owls-api/target/classes/META-INF/MANIFEST.MF</manifestFile>
> <compress>true</compress>
> <manifest>
> <addClasspath>false</addClasspath>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> </archive>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-166) Merging with existing MANIFEST.MF
looses Class-Path element
Posted by "Thorsten Möller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238316#action_238316 ]
Thorsten Möller commented on MSHARED-166:
-----------------------------------------
Sorry, hit the create button too soon. In the following more detailed description.
I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data for the MANIFEST.MF(_maven-bundle-plugin) file). In short, the bundle plugin creates a MANIFEST.MF file containing all OSGi related meta data. This file is taken and merged by the jar plugin into the final MANIFEST.MF file (note that the documentation http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html states "The content of your own manifest file will be merged with the entries generated by Maven Archiver.").
The problem is that the "Class-Path" property gets lost although configuration of the jar plugin is set to create it, see MANIFEST.MF_final_with_maven-bundle-plugin. When the build runs without the bundle plugin (by deactivating corresponding lines in the POM) the "Class-Path" property exists, see MANIFEST.MF_final_without_maven-bundle-plugin. This makes me believing that there is a bug in either the jar or the archiver plugin.
> Merging with existing MANIFEST.MF looses Class-Path element
> -----------------------------------------------------------
>
> Key: MSHARED-166
> URL: http://jira.codehaus.org/browse/MSHARED-166
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Reporter: Thorsten Möller
> Attachments: MANIFEST.MF_final_with_maven-bundle-plugin, MANIFEST.MF_final_without_maven-bundle-plugin, MANIFEST.MF_maven-bundle-plugin
>
>
> I'm using the maven-bundle-plugin together with the maven-jar-plugin (to create OSGi meta data). The plugin configuration is as follows (excerpt from effective POM):
> {code:xml}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <version>2.1.0</version>
> <extensions>true</extensions>
> <executions>
> <execution>
> <goals>
> <goal>manifest</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <instructions>
> <Export-Package>org.mindswap.*</Export-Package>
> <Private-Package>impl.*</Private-Package>
> <RequiredExecutionEnvironment>J2SE-1.5</RequiredExecutionEnvironment>
> </instructions>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.3.1</version>
> <configuration>
> <archive>
> <manifestFile>/Users/thorsten/development/on/owls-api/target/classes/META-INF/MANIFEST.MF</manifestFile>
> <compress>true</compress>
> <manifest>
> <addClasspath>false</addClasspath>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> </archive>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira