[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for achetypes

["Herve Boutemy (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277418#comment-277418 ] 

Herve Boutemy commented on ARCHETYPE-302:
-----------------------------------------

documentation of [the whole archetype lifecycle|http://maven.apache.org/archetype/maven-archetype-plugin/] has been added
from what I understand, you propose to make the "archetype project" step disappear, which will streamline the archetype creation from example project

question: where do you see the archetype descriptor in the example project? how to have a maven-archetype packaging without disturbing the example project?
(less critical at a first glance: and what about integration tests ?)

> Have a custom packaging type for achetypes
> ------------------------------------------
>
>                 Key: ARCHETYPE-302
>                 URL: https://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.
For more information on JIRA, see: http://www.atlassian.com/software/jira