[
https://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279055#comment-279055
]
Hardy Ferentschik edited comment on ARCHETYPE-302 at 9/15/11 7:40 AM:
----------------------------------------------------------------------
{quote}
from what I understand, you propose to make the "archetype project" step
disappear, which will streamline the archetype creation from example project
{quote}
correct
{quote}
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 ?)
{quote}
the archetype descriptor could be in a default location which is excluded from
the final archetype, eg _src/main/archetype_. This could even be configured via
a property.
Regarding the packaging, It would be nice to be able to have an alternative
_pom.xml_ or at least more flexibility to configure the resulting pom. For
example, the dependencies and build configuration is really the core thing I
want to get into the archetype. For things like, description, developer, etc I
would like to be able to override/customize the pom. (Note, I used to not even
specify things like developer and scm in the pom which formed the based for the
archetype, but since the Sonar instance I am deploying into has some pom
validation rules which require these settings.)
was (Author: esfahan):
{quote}
from what I understand, you propose to make the "archetype project" step
disappear, which will streamline the archetype creation from example project
{quote}
correct
{quote}
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 ?)
{quote}
the archetype descriptor could be in a default location which is excluded from
the final archetype, eg _src/main/archetype_. This could even be configured via
a property.
Regarding the packaging, It would be nice to be able to have an alternative
_pom.xml_ or at least more flexibility to configure the resulting pom. For
example, the dependencies and build configuration is really the core thing I
want to get into the archetype. For things like, description, developer, etc I
would like to be able to override/customize the pom. (Note, I used to not even
specify things like developer and scm in the pom which formed the based for the
archetype, but since the Sonar instance I am deploying into has some pom
validation rules which require these settings.
> 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
