Jason, this is not about mimicking old behaviour. The new code is plain wrong for this case. When you define the archetype's groupId, artifactId and version on command line, the plugin should not offer you a list to pick from. That's especially tragic when the archetype you want is not in the list. Period. If all archetype properties are defined, it should just create the project, if some are missing ask for missing values. Catalogues should help, not be in the way.
The only workaround I figured out, is to run maven in batch mode and declare archetype ids and all properties on command line. Strangely enough the central repository needs to be declared on command line as well. I'm for calling this a bug too. Milos On Feb 12, 2008 4:30 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > We can create a new goal name, whatever it be, and mimic the old > behavior. > > The archetypes don't need to reside in central. I've been taking the > list off the Wiki and turning it into the internal catalog. We can > keep the list itself in that case for the command line. For the > Eclipse use case we can read the internal catalog, or the Nexus index > source which does require the Archetypes to be in central. And what's > the problem with that in your case if you're syncing to central. > > At any rate, we can fix that goal and mimic the new behavior. Might be > good to try and raise these things when we've asked repeatedly for > people to try it. Most people seem to hate that notation below so I > asked Raphael to make the batch mode non-default and provide the list. > > > On 12-Feb-08, at 7:02 AM, Daniel Kulp wrote: > > > > > The new archetype plugin seems to have broken the normal > > instructions on > > how to create new projects. It doesn't seem to work. > > > > For example, according to: > > http://cwiki.apache.org/confluence/display/CAMEL/Creating+a+new+Spring+based+Camel+Route > > > > I should just need to run: > > mvn archetype:create \ > > -DarchetypeGroupId=org.apache.camel \ > > -DarchetypeArtifactId=camel-router \ > > -DarchetypeVersion=1.1.0 \ > > -DgroupId=myGroupId \ > > -DartifactId=myArtifactId > > > > > > That worked last week. Now I get a big list of archetypes to select > > from and the camel stuff isn't there. > > > > > > So, how the heck is this now supposed to work? If projects have > > archetypes in central, how are users supposed to use them? I really > > think we need to get a new version out that allows the previous > > instructions to work. This really breaks a BUNCH of projects > > instructions for creating samples/projects. > > > > > > -- > > J. Daniel Kulp > > Principal Engineer, IONA > > [EMAIL PROTECTED] > > http://www.dankulp.com/blog > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > jason at sonatype dot com > ---------------------------------------------------------- > > happiness is like a butterfly: the more you chase it, the more it will > elude you, but if you turn your attention to other things, it will come > and sit softly on your shoulder ... > > -- Thoreau > > > > > > --------------------------------------------------------------------- > 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]
