I have also run into this. We created some code to autogenerate some stuff for us. The most logical thing to do is make this a mojo and use it in the build. The trouble is that this code requires some stuff we would be concurrently building. (not generating, but part of the same tree).
-----Original Message----- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, June 30, 2006 11:46 AM To: Maven Developers List Subject: Building and using a plugin in the same build (m2) In geronimo, we have a plugin that uses a lot of core geronimo functionality, that we would like to use to construct pieces of the server. We seem to have run into a design decision of m2 that a plugin cannot be built and used in the same build. Is this correct, or are we doing something wrong? Assuming this is correct, what is the thinking behind it? To me, it seems like any project with any framework aspirations is almost certain to want to use pieces of itself to build itself, and the only way I know of to do this in maven is to write a plugin. So, is the intention in maven really to force any such project to split the build up into at least two phases, the first where the stuff the plugin uses is built + the plugin, the second the stuff that uses the plugin? To me this seems like close to a showstopper for using maven. thanks david jencks --------------------------------------------------------------------- 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]
