On 17/11/2007, Wouter de Vaal <[EMAIL PROTECTED]> wrote: > > Hi, > > I finally gotten around to giving the pax construct cloning process > another spin (this time from 0.1.6 to 0.5.1), and I have some more issues: > > The parent pom contains this as id: > > <groupId>com.<mydomain></groupId> > <artifactId>project</artifactId> > <version>1.0.0-SNAPSHOT</version> > > and the modules are like this: > > <groupId>com.<mydomain></groupId> > <artifactId>jetty</artifactId> > <version>1.0.0-SNAPSHOT</version> > > Now the cloning process keeps the parent pom in order, but changes the > module poms like this: > > <groupId>com.<mydomain>.project</groupId> > <artifactId>jetty</artifactId> > <version>1.0.0-SNAPSHOT</version> > > > I don't what .project added to the groupId's as I think it is ugly, but I > need an artifactId for the parent pom, so, thats just called "project" for > mavens sake. Is there any solution to this?
yep, I've opened http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-48 to look into this basically, the pax-create-bundle and pax-wrap-jar commands will accept an option to set the groupId, and the pax-clone command will use this to keep the current groupId a working solution will be in 0.6.1, which I'll release this weekend HTH Thanks, > Wouter > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Cheers, Stuart
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
