You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike Haney (JIRA)" <ji...@codehaus.org> on 2009/02/20 02:24:20 UTC
[jira] Created: (ARCHETYPE-227) spring-osgi-bundle-archetype
generates incorrect pom
spring-osgi-bundle-archetype generates incorrect pom
----------------------------------------------------
Key: ARCHETYPE-227
URL: http://jira.codehaus.org/browse/ARCHETYPE-227
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Environment: Tested on Windows using Maven 2.0.9 and 2.0.10 and Ubuntu 8.10 using Maven 2.0.9
Reporter: Mike Haney
Priority: Minor
Attachments: package_out.txt
Running 'mvn archetype:generate' and choosing spring-osgi-bundle-archetype (currently #24) generates code that results in build errors with subsequent runs of 'mvn package'. Attached is the output of a run showing the error and stack trace (package_out.txt).
Upon investigation, it appears that the generated pom.xml is specifying version 1.0.0 of the maven-bundle-plugin as such:
{code:xml}
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<extensions>true</extensions>
<version>1.0.0</version>
<configuration>
<manifestLocation>META-INF</manifestLocation>
<instructions>
<Export-Package>!com.example.spring.osgi.impl,com.example.spring.osgi*</Export-Package>
<Import-Package>*</Import-Package>
<!--
add ,plugin.xml if it's present i.e.
src/main/resources,plugin.xml
-->
<Include-Resource>src/main/resources</Include-Resource>
</instructions>
</configuration>
</plugin>
{code}
Manually removing the version specification (or less-elegantly, hardcoding the current version) resolves this issue so that the build can complete.
It would be nice to modify the generator plugin so that the pom.xml is generated WITHOUT the version specification for the maven-bundle-plugin.
--
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] Updated: (ARCHETYPE-227) spring-osgi-bundle-archetype
generates incorrect pom
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated ARCHETYPE-227:
------------------------------------
Component/s: (was: Generator)
Archetypes
> spring-osgi-bundle-archetype generates incorrect pom
> ----------------------------------------------------
>
> Key: ARCHETYPE-227
> URL: http://jira.codehaus.org/browse/ARCHETYPE-227
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
> Environment: Tested on Windows using Maven 2.0.9 and 2.0.10 and Ubuntu 8.10 using Maven 2.0.9
> Reporter: Mike Haney
> Priority: Minor
> Attachments: package_out.txt
>
>
> Running 'mvn archetype:generate' and choosing spring-osgi-bundle-archetype (currently #24) generates code that results in build errors with subsequent runs of 'mvn package'. Attached is the output of a run showing the error and stack trace (package_out.txt).
> Upon investigation, it appears that the generated pom.xml is specifying version 1.0.0 of the maven-bundle-plugin as such:
> {code:xml}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <extensions>true</extensions>
> <version>1.0.0</version>
> <configuration>
> <manifestLocation>META-INF</manifestLocation>
> <instructions>
> <Export-Package>!com.example.spring.osgi.impl,com.example.spring.osgi*</Export-Package>
> <Import-Package>*</Import-Package>
> <!--
> add ,plugin.xml if it's present i.e.
> src/main/resources,plugin.xml
> -->
> <Include-Resource>src/main/resources</Include-Resource>
> </instructions>
> </configuration>
> </plugin>
> {code}
> Manually removing the version specification (or less-elegantly, hardcoding the current version) resolves this issue so that the build can complete.
> It would be nice to modify the generator plugin so that the pom.xml is generated WITHOUT the version specification for the maven-bundle-plugin.
--
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: (ARCHETYPE-227) spring-osgi-bundle-archetype
generates incorrect pom
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed ARCHETYPE-227.
-----------------------------------
Resolution: Won't Fix
Assignee: Herve Boutemy
this archetype isn't maintained by Maven team, but by SpringSource
Maven team can't do anything to fix this archetype
> spring-osgi-bundle-archetype generates incorrect pom
> ----------------------------------------------------
>
> Key: ARCHETYPE-227
> URL: http://jira.codehaus.org/browse/ARCHETYPE-227
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
> Environment: Tested on Windows using Maven 2.0.9 and 2.0.10 and Ubuntu 8.10 using Maven 2.0.9
> Reporter: Mike Haney
> Assignee: Herve Boutemy
> Priority: Minor
> Attachments: package_out.txt
>
>
> Running 'mvn archetype:generate' and choosing spring-osgi-bundle-archetype (currently #24) generates code that results in build errors with subsequent runs of 'mvn package'. Attached is the output of a run showing the error and stack trace (package_out.txt).
> Upon investigation, it appears that the generated pom.xml is specifying version 1.0.0 of the maven-bundle-plugin as such:
> {code:xml}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <extensions>true</extensions>
> <version>1.0.0</version>
> <configuration>
> <manifestLocation>META-INF</manifestLocation>
> <instructions>
> <Export-Package>!com.example.spring.osgi.impl,com.example.spring.osgi*</Export-Package>
> <Import-Package>*</Import-Package>
> <!--
> add ,plugin.xml if it's present i.e.
> src/main/resources,plugin.xml
> -->
> <Include-Resource>src/main/resources</Include-Resource>
> </instructions>
> </configuration>
> </plugin>
> {code}
> Manually removing the version specification (or less-elegantly, hardcoding the current version) resolves this issue so that the build can complete.
> It would be nice to modify the generator plugin so that the pom.xml is generated WITHOUT the version specification for the maven-bundle-plugin.
--
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