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

Hardy Ferentschik commented on ARCHETYPE-302:
---------------------------------------------

{quote}The idea when you've created once the archetype from a sample project is 
to put the generated source tree in your scm and start improving it: the 
archetype project is a full project see maven-archetype-bundles svn to see it 
in action{quote}
I think there is my problem. If I check in the sources generated by 
'archetype:create-from-project' the java files become template files which 
means that IDEs cannot parse/import the project sources. However, having the 
archetype sources as "normal" project helps to maintain the archetype, since 
API changes etc can easily be refactored. 

{quote}
Or you're in the case where the archetype automatically created from a project 
is always sufficient.
{quote}
The whole purpose of the module I have is to be the template of the archetype, 
so yes it would be sufficient. Well, I would like to make some modifications to 
the pom, but the sources are correct. 


> 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

        

Reply via email to