RE: Can a project use a plugin that is part of the project - bootstrap issue
Matt, There was a similar post over the weekend http://www.nabble.com/Impossible-to-build-ourproject-from-scratch-tf2519 755s177.html#a7027880 Hope it helps. William > -Original Message- > From: J. Matthew Pryor [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 31 October 2006 9:18 AM > To: Maven Users List > Subject: Can a project use a plugin that is part of the > project - bootstrap issue > > I am trying to work through a "boot-strap" issue. > > Currently we have a multi-project that includes a > maven-plugin module that is then used to build other modules > in the multi-project. > > As you might expect a clean checkout & build at the top-level > fails because mvn says it can't find the plugin in question > (it hasn't been built yet). > > Is there any way to do this? Or do I have to break the plugin > out into its own project & build it separately? > > Thanks, > Matthew > > p.s. I posted this question once before but did so as a reply > and was worried it got lost in that noise, apologies for the > duplication > > - > 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]
Re: Can a project use a plugin that is part of the project - bootstrap issue
OK so it seems my nabble searching is pretty lousy ... there was a similar post recently The solution I have come up with is to use profiles in the top-level POM to contain the modules declarations I create a bootstrap profile which contains the minimal modules, then an 'all' profile that contains all modules and has true So the fresh top level build does this: mvn -P bootstrap clean install That seems to work fine Cheers, jmp J. Matthew Pryor wrote: I am trying to work through a "boot-strap" issue. Currently we have a multi-project that includes a maven-plugin module that is then used to build other modules in the multi-project. As you might expect a clean checkout & build at the top-level fails because mvn says it can't find the plugin in question (it hasn't been built yet). Is there any way to do this? Or do I have to break the plugin out into its own project & build it separately? Thanks, Matthew p.s. I posted this question once before but did so as a reply and was worried it got lost in that noise, apologies for the duplication - 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]
