I'm not so sure if we can really use that much of the pax plugin. There is much structure and logic you typically do not use for a karaf project. The question is: what exactly do you want the archetype for: a) a multiproject karaf project or b) a single module. Both would be completely different from the current pax structure. I would suggest not to use e.g. those osgi files but rather define the logic directly in the pom. In addition I would suggest to not use the parents/xxx pom structure but rather a clean head <- child structure straight from the top to the bottom. In addition we'll need a features/assembly project instead of the provision folder. I think that's all.
WDYT? Kind regards, Andreas On Thu, Dec 15, 2011 at 18:15, Matt Madhavan <[email protected]> wrote: > Hello JB and Achim, > Maven Pax Plugin might be a good starting point. Looks like it has not been > updated for a while and does not work well at all with m2eclipse(When you > try to create a bundle it totally cobbers the parent pom) and its tailored > more towards PaxRunner. > > But I'm sure we can borrow lots of base knowledge and code from this. > > Just a thought! > > Thanks > Matt > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Basic-question-Maven-Plugin-for-creating-Parent-Projects-Bundle-projects-tp3586378p3589266.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
