Stephen wrote: > 1. if your integration test is run using, eg maven-invoker-plugin or one of > the other tools, > then it will not be going to be deployed on repo1.maven.org, so you do not > need to > inherit those IT poms from mojo-parent
I made this recommended change on CBUILDS and it works after a bit of hacking, thanks. Dan wrote: >May be we could split mojo-parent into 2? :-) the top one is reusable, > the other one is MOJO specific Yeah, I was thinking the same, have "plugin-parent" and "mojo-parent". Stephen and Benjamin are -1 on that idea. ________________________________ From: Dan Tran <[email protected]> To: [email protected] Sent: Tue, December 1, 2009 8:12:15 PM Subject: Re: [mojo-dev] [VOTE] Release Mojo Parent POM 23 I think mojo-parent is a very good start since it is tested by many of its sub project. May be we could split mojo-parent into 2? :-) the top one is reusable, the other one is MOJO specific -Dan On Tue, Dec 1, 2009 at 3:05 PM, Lee Thompson <[email protected]> wrote: > Benjamin wrote: >>Just keep in mind that the Archetye Plugin itself "instantiates" >> archetypes. So when you talk about "adds no project infrastructure" it's not >> an issue of the plugin but a matter of creating an archetype that fits your >> needs. > > Check this out! This runs > > mvn archetype:create -DgroupId=com.myco.quickplugin \ > -DartifactId=test-plugin \ > -DarchetypeGroupId=org.apache.maven.archetypes \ > -DarchetypeArtifactId=maven-archetype-plugin > > maven-archetype-plugin is a plugin and an archetype > > http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-4/ > http://repo2.maven.org/maven2/org/apache/maven/archetypes/maven-archetype-plugin/1.0/ > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
