Community
Participate
Working Groups
Build Identifier: RC1 The command: mvn archetype:generate -DarchetypeGroupId=org.springframework.osgi -DarchetypeArtifactId=spring-osgi-bundle-archetype -DgroupId=foo -DartifactId=bar -DarchetypeVersion=1.2.1 -Dversion=0.0.0 -DinteractiveMode=false generates a pom.xml with an incorrectly configured com.springsource.bundlor plugin: its outputManifest tag points one directory "above" where it should, e.g., at /a/META-INF/MANIFEST.MF rather than /a/b/META-INF/MANIFEST.MF where 'a' is the directory where the command was executed and 'b' is the artifactId. Reproducible: Always Steps to Reproduce: 1. cd /tmp 2. mvn archetype:generate \ -DarchetypeGroupId=org.springframework.osgi \ -DarchetypeArtifactId=spring-osgi-bundle-archetype \ -DgroupId=foo \ -DartifactId=bar \ -DarchetypeVersion=1.2.1 \ -Dversion=0.0.0 \ -DinteractiveMode=false 3. cd /tmp/bar 4. grep outputManifest pom.xml 5. the result will be /tmp/META-INF/MANIFEST.MF not /tmp/bar/META-INF/MANIFEST.MF
The spring-osgi-bundle-archtetype support is not part of Virgo or Virgo's tooling. I think it's associated with the Spring DM project, so I'm assigning to Gemini Blueprint (the follow-on to Spring DM).
It seems the archetype support was not contributed to Gemini Blueprint, so it's not going to be possible to fix that bug here. [org.eclipse.gemini.blueprint master]$ grep -r bundle-archetype . [org.eclipse.gemini.blueprint master]$
