You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org> on 2010/05/04 13:29:12 UTC
[jira] Created: (ARCHETYPE-302) Have a custom packaging type for
achetypes
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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220596#action_220596 ]
Herve Boutemy commented on ARCHETYPE-302:
-----------------------------------------
there is already a "maven-archetype" packaging
And I don't understand your use case: archetypes have normal release process.
Or you're in the case where the archetype automatically created from a project is always sufficient.
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
> 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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279055#comment-279055 ]
Hardy Ferentschik commented on ARCHETYPE-302:
---------------------------------------------
{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
[jira] Issue Comment Edited: (ARCHETYPE-302) Have a custom
packaging type for achetypes
Posted by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221000#action_221000 ]
Herve Boutemy commented on ARCHETYPE-302:
-----------------------------------------
interesting idea: need to think at it (no time at the moment, but I like the idea as it is re-phrased)
> 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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (ARCHETYPE-302) Have a custom packaging type for
achetypes
Posted by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org>.
[ 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