I wouldn't presume calling myself a maven guru :) but i recently build an archetype myself too. I wonder why you have to use resource in your archetype. i get that your archetype is a maven multiproject but i don't see how using resource is better then using source. I am just guessing here but what if use source instead of resource and add a modules element to the relevant pom.
A different solution would be to not include that code as modules but as dependencies to a jar, that way you can avoid all the problems. Maurice BTW just looking at the wicket archetype has helped me very much. On Mon, Jun 30, 2008 at 7:24 PM, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > Hi > > Could some maven guru please take a look at wicket iolite..? The problem are > that it is a multi module project, so in order to get it working I had to > map everything as resources in the archetype .xml , this it not good > because the java package mojo does not look on these files meaning that java > packages arent supported:( > > -- > -Wicket for love > > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
