Thanks for your answers! Is there a way you could add the 2 links [0][1] you posted to the mojo dev guildelines [3]? ;)
If there is not much difference between the 2 parent poms, I will go the official way starting with the sandbox parent. Txs and LieGrue, strub [3] http://mojo.codehaus.org/development/guidelines.html --- Benjamin Bentmann <[email protected]> schrieb am Di, 17.2.2009: > Von: Benjamin Bentmann <[email protected]> > Betreff: Re: [mojo-dev] Question about Mojo Dev Guildelines page > An: [email protected] > Datum: Dienstag, 17. Februar 2009, 12:32 > Mark Struberg wrote: > > > So are sandbox plugins not ment to be released? > > Yup, the sandbox parent explicitly overrides > <distributionManagement> to prevent releases, see also > [0]. AFAICT, the sandbox is a place to hack around until > something is approved by the community for public > consumption. > > > Should I use the mojo-sandbox-parent or the > mojo-parent (which it uses until now) for this plugin? > > Technically, there is not much difference between the > regular mojo-parent and the mojo-sandbox-parent, apart from > the dist repo. I.e. whatever parent you choose for the > initial import it shouldn't have effects on the > deployment of snapshots and the site. If you intend to > graduate the new plugin [1] soon out of the sandbox, I doubt > anybody here has concerns when you inherit from the > mojo-parent right from the start. > > > Benjamin > > > [0] http://mojo.codehaus.org/faq.html#what-is-the-sandbox > [1] > http://mojo.codehaus.org/development/performing-a-release.html#Graduating_from_the_Sandbox --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
