Thanks Willem. I hope issue 1 (archetype-catalog.xml issue) will be fixed too..
willem.jiang wrote: > > For the issue 2, it is already be fixed in Camel 2.2-SNAPSHOT[1] a week > ago. > > [1] https://issues.apache.org/activemq/browse/CAMEL-2313 > > Willem > > Hendy Irawan wrote: >> Creation of new Camel project with Camel archetype version 2.1.0 is >> unusable. >> This feature is very useful to speed up Camel app development (and quick >> testing of ideas). >> >> Due to two separate reasons: >> >> 1. There's no archetype-catalog.xml on both: >> >> http://repo1.maven.org/maven2/archetype-catalog.xml >> https://repository.apache.org/content/repositories/releases/archetype-catalog.xml >> >> I used to be able to select the archetype I need visually. Now I need to >> manually specify the group/artifact/version. >> >> With latest archetype plugin, no proper archetype-catalog.xml means >> archetype plugin is, for all purposes, useless. See: >> http://jira.codehaus.org/browse/ARCHETYPE-242 >> >> 2. The generated project is incorrect, for example the generated POM >> contains: >> >> ... >> <groupId>${project.groupId}</groupId> >> <artifactId>${project.artifactId}</artifactId> >> ... >> >> instead of the given project group/artifact Ids. > > > -- View this message in context: http://old.nabble.com/Camel-archetype-2.1.0-unusable%3A-archetype-catalog.xml-and-generated-project-tp26969866p26975513.html Sent from the Camel - Users mailing list archive at Nabble.com.
