"Tomas Carlsson" <[EMAIL PROTECTED]> writes: > Hi, > > My initial thought is to create a plugin that first generates sources for > the different purposes, then compiles them and lastly packages one archive > for each type. > > I.e: > 1 input file => 3 generated source trees => 3 compiled "classes" tress => > 3 packed archetypes > > I'm seeing some trouble with this though: > > 1. It violates the maven philosophy of only having one archetype > 2. The plugin seems to get quite complicated which I think should be > possible to avoid >
Hello Tomas, I wrote a code generation plugin that does different things, ie. have different mojos. I do not think this is complicated as this seems to be the norm. As for Q.1, I do not have any definitive answer but what I did in my case was creating one subproject for each different generation process with dependency on the model project. Then you can configure your plugin to do one thing in each project before compile or anything else, then generate one artifact per project which is compliant with standard maven usage. HTH, -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
