On 13/02/2008, Stefan Hübner <[EMAIL PROTECTED]> wrote: > > Hi everybody, > > does anybody experience the same issue like me since updating to the > latest maven-archetype-plugin? I'm trying to create a new project by > invoking e.g. (taken directly from > http://mojo.codehaus.org/groovy/groovy-maven-archetype/index.html) > > mvn archetype:create \ > -DarchetypeGroupId=org.codehaus.mojo.groovy \ > -DarchetypeArtifactId=groovy-maven-archetype \ > -DgroupId=com.mycompany \ > -DpackageName=com.mycompany.mymodule \ > -DartifactId=mymodule > > When invoking this the archetype-plugin asks me to pick one of the > standard-archetypes. the groovy-archetype isn't even listed, although > is resides in my local repo. > > What's going on?
I think you've picked up the new release of the archetype plugin which by default runs in interactive mode, with choices from an internal catalog (even when the archetype groupId and artifactId are already selected) this has been raised and discussed on the developer list: http://www.nabble.com/New-archetype-plugin-issues-questions....-td15435079s177.html and a fix is in progress, until a new release is made you can use: mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create ...etc... to force Maven to use the old version :( -Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
