Archetype install process substitutes package names when creating modular
projects
----------------------------------------------------------------------------------
Key: ARCHETYPE-356
URL: http://jira.codehaus.org/browse/ARCHETYPE-356
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Affects Versions: 2.0
Reporter: Matt Raible
AppFuse has a number of imports that are contained in JARs. Therefore, after
running "archetype:generate", I use Ant to change some imports from
${package}.foo to org.appfuse.foo.
<replace dir="@{dir}/target/generated-sources/archetype/src">
<replacetoken>import ${package}.model</replacetoken>
<replacevalue>import org.appfuse.model</replacevalue>
</replace>
This works for single-module projects. However, on multi-module projects, even
though the source has "org.appfuse", something in the archetype JAR-ing changes
org.appfuse to ${package}.
This does *not* happen when using the 2.0-alpha-4 version of the plugin.
To reproduce, use the attached project and run "mvn install" on it, then create
a new project using it.
archetype:generate -B -DarchetypeGroupId=org.appfuse.archetypes
-DarchetypeArtifactId=myproject -DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.mycompany -DartifactId=appfuse-modular-spring-archetype
-DpackageName=com.mycompany -DarchetypeRepository=local
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
