camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Anstey <jans...@gmail.com>
Subject Re: The latest camel java archetype (2.1.0) is not working correctly
Date Wed, 23 Dec 2009 19:39:13 GMT
Darn! Looks like a change I made to support Maven 3 broke Maven 2. I've put
a fix on trunk so the artifact/group substitution will work for next time.

On Wed, Dec 23, 2009 at 2:59 PM, Ryadh Amar <magnetic.ganesh@gmail.com>wrote:

>
> Hello Community,
> When I run the following
> mvn archetype:generate -DarchetypeGroupId=org.apache.camel.archetypes
> -DarchetypeArtifactId=camel-archetype-java -DarchetypeVersion=2.1.0
> -DgroupId=com.corp.projects -DartifactId=camel-jira-ws
> Everything looks ok, but glancing at the generated pom.xml in the newly
> created project, it seems the archetype didn't pick the groupId and the
> artifactID
>
> =================================
>  <groupId>${project.groupId}</groupId>
>  <artifactId>${project.artifactId}</artifactId>
>  <packaging>jar</packaging>
>  <version>1.0-SNAPSHOT</version>
> =================================
>
> the 2.0.0 archetype works fine.
> just a FYI
>
> Should a JIRA issue be raised?
> --
> View this message in context:
> http://old.nabble.com/The-latest-camel-java-archetype-%282.1.0%29-is-not-working-correctly-tp26905679p26905679.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


-- 
Cheers,
Jon

Camel in Action: http://manning.com/ibsen
Blog: http://janstey.blogspot.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message