[
https://jira.codehaus.org/browse/ARCHETYPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325970#comment-325970
]
Julien Torrielli commented on ARCHETYPE-422:
--------------------------------------------
I finally found a solution. This is not really a bug, your modules name need to
have the same name as your folders. For instance you have this :
.
|-- app
| `-- pom.xml
|-- config
| `-- pom.xml
|
`-- pom.xml
In your root pom, you need to specify
<modules>
<module>app</module>
<module>config</module>
</modules>
And in your modules pom :
<artifactId>app</artifactId>
<artifactId>config</artifactId>
> Unable to find resource 'archetype-resources/*/pom.xml'
> -------------------------------------------------------
>
> Key: ARCHETYPE-422
> URL: https://jira.codehaus.org/browse/ARCHETYPE-422
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
> Environment: Windows 7, Apache Maven 3.0.4 (r1232337; 2012-01-17
> 00:44:56-0800)
> Java version: 1.6.0_30, vendor: Sun Microsystems Inc.
> Reporter: Aleksei Serov
> Priority: Minor
> Attachments: archetype.zip
>
>
> I am running a mvn archetype:generate on multi-module project archetype I
> have created using mvn archetype:create-from-project and mvn install.
> Archetype attached.
> I get:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on
> project standalone-pom:
> org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error
> merging velocity templates: Unable to find resource
> 'archetype-resources/*/pom.xml' -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate
> (default-cli) on project standalone-pom:
> org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error
> merging velocity templates: Unable to find resource
> 'archetype-resources/*/pom.xml'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
