[
http://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220938#action_220938
]
Hardy Ferentschik commented on ARCHETYPE-302:
---------------------------------------------
Maybe I should re-phrase a little. I think that it would be great if the
project/module which should become the archetype could exist in its "extracted"
form, be it a webapp, spring-, hibernate- or whatever-app. This makes it easy
to evolve the artifact. At install/deploy time I everything to get packaged
into a archetype. The one thing I would like to change/modify is the pom.
> Have a custom packaging type for achetypes
> ------------------------------------------
>
> Key: ARCHETYPE-302
> URL: http://jira.codehaus.org/browse/ARCHETYPE-302
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Creator
> Reporter: Hardy Ferentschik
>
> Currently if you want to create an archetype from a existing project you need
> a two step process. First you have to run 'mvn archetype:create-from-project'
> and then you have to install/deploy the archetype generated in
> {{target/generated-sources/archetype}}. Wouldn't it be possible to have a new
> packaging type, eg archetype?
> For example, imagine you have an aggregator (multi module) project, where one
> module is supposed to be the template for the archetype. When you
> deploy/release the whole project you would like the archetype creation be
> part of the the 'mvn deploy' or 'mvn release:perform' process. Currently you
> will have to go through the mentioned two step process.
> Thoughts?
--
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
