Dear Gert, >This appears to be a 'feature' of the latest release of Maven's >archetype plugin. For now, a workaround could be to define a local >archetype catalog. This is a file named ~/.m2/archetype-catalog.xml in >which you define the ServiceMix archetypes you want to use. An example:
><?xml version="1.0" encoding="utf-8"?> ><archetype-catalog> > <archetypes> > <archetype> > <groupId>org.apache.servicemix.tooling</groupId> > <artifactId>servicemix-service-unit</artifactId> > <version>3.2.1</version> > <repository>http://repo1.maven.org/maven2</repository> > <description>ServiceMix archetype for creating a simple >SU</description> > </archetype> > </archetypes> ></archetype-catalog> >Off course, you would also have to add all the orther archetypes you >want to use. After that, you can use "mvn archetype:create >-DarchetypeCatalog=local" to bring up the same menu as you mention in >your post, but with the ServiceMix archetypes in there. Maven will also >prompt you for all the additional information it needs. Let's hope they >will support the original way of doing things as well again in there >next release, but in the meanwhile: could you open a JIRA issue so we >can provide a ServiceMix archetype-catalog somewhere on the web for all >our users ASAP. thank you, with your help I was able to work through the sample. I have opened a JIRA issue SM-1224 for the component "archetypes": http://issues.apache.org/activemq/browse/SM-1224 Kind regards, Frank
