On 25 Sep 2011, at 22:45, Matt Madhavan wrote: > Hello, > When I tried to create a child bundle project from eclipse using the > maven-archetype-osgi-bundle I found couple of issues. I right cliked on the > Parent project and did new Maven --> module and chose > maven-archetype-osgi-bundle (I'm using 1.5) > > 1. It just smothers the parent pom (Every thing gets deleted and f new lines > added). > 2. The bundle symbolic name gets messed up. The artifact id = > com.hcsc.ccsp.common.om.feature but the symbolic name created is: > com.hcsc.ccsp.common.om.feature.com.hcsc.ccsp.common.om.feature while I was > expecting just com.hcsc.ccsp.common.om.feature > > But when I use 1.0 the first problem does not happen. The second issue > happens. > > Can some one take a look at it please?
The pax-construct archetypes won't work properly when used via the Maven archetype plugin - this is because at the time they were written the archetype plugin didn't support any of the filtering, post-creation-hook, and pom traversal features needed to properly wire the new module into an existing project. That's why you see odd results, such as the parent pom getting overwritten instead of being merged. Instead you need to use the CLI pax-construct commands (or the maven-pax-plugin goals) to apply these archetypes, which add the necessary functionality. > Thanks > Matt > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
