Thanks to everybody who helped with ideas for the war packaging. I think the two best solutions are: 1. multi-module project 2. generate-sources phase.
I actually like the best number 2, because we include in our classes the ones which are generated so i would like to keep them in the same module. As such I will look into implementing that one. thanks again, Attila > Date: Thu, 31 Aug 2006 08:54:31 -0400 > From: "Jared Bunting" <[EMAIL PROTECTED]> > To: "Maven Users List" <[email protected]> > Subject: Re: Re: mvn2: war packaging > > I might be missing what you're trying to do here, > and it seems to me that > creating a multi-module project, as suggested, would > be the best way to go > about this. However, what if you bound your source > generation to the > "generate-sources" phase. I'm not sure of how it > would be done in ant, but > I know that you can then "add" the generated sources > to the list of files to > compile in the compile phase and then they should be > included in your > WEB-INF/classes directory in the war file. They > won't be in a jar, but > they'll be in your war. > > (and you can DEFINITELY guarantee that they will be > generated before the war > is created - it seems that they are getting > generated after the war because > you are binding to the packaging phase, which is > meant to actually package, > and plugin order within a phase is undefined...) > > I found an article that mentions doing this with a > hibernate ant task here: > > http://www.onjava.com/pub/a/onjava/2005/12/14/hibernate-class-generation-with-hbm2java.html?page=4 > > Maybe this will be helpful? > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
