I understand your desire for "not wanting things too complex" but, in maven, it's important to follow one simple rule:
Every pom.xml (maven project) _should_ produce exactly one file as a resulting artifact If you need two files (a .jar and a .war) then you need two pom.xml (maven projects) and it's actually very very easy to split things up that way. Yes, it does take some adjusting to use this model, and yes it can be quite difficult sometimes to follow "hey, why is it doing that here?" but in the end, if you follow the maven model, you might find it makes more sense to do it "the maven way". (and if you don't like splitting it up, I would DEFINITELY recommend using Ivy or something: maven works wonders when it's used "the maven way" and causes no end of headache when you try to twist it do something else....) Dana Lacoste -----Original Message----- From: Cecchi Sandrone [mailto:[email protected]] Sent: Tuesday, January 12, 2010 1:34 PM To: [email protected] Subject: Re: Assembly as dependency of the same project Just to maintain the things not too complex. Furthermore, the same behavior I described is needed for XmlBeans class generation. I have a set of classes generated from XSDs and I want to package them into a jar and put it as a dependency of the project. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
