You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rod Coffin (JIRA)" <ji...@codehaus.org> on 2007/01/16 22:47:41 UTC
[jira] Created: (ARCHETYPE-64) groupId and version redundant when
executing archetype with parent
groupId and version redundant when executing archetype with parent
------------------------------------------------------------------
Key: ARCHETYPE-64
URL: http://jira.codehaus.org/browse/ARCHETYPE-64
Project: Maven Archetype
Issue Type: Improvement
Components: Archetypes
Affects Versions: 1.0-alpha-4
Reporter: Rod Coffin
Running the archetype plugin in a parent project creates a sub-project (module). Although the parent elements are properly set in the child pom, the group id and version are repeated. These are not necessary since they will be inherited from the parent. Ex:
<parent>
<artifactId>parent</artifactId>
<groupId>com.rfc.archetypes.example</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>com.rfc.archetypes.example</groupId>
<artifactId>example-web</artifactId>
<version>1.0-SNAPSHOT</version>
Having this information is two places is bad in principle because it violates the DRY principle and in practice because they can get out of sync accidentally and it could be confusing.
--
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] Updated: (ARCHETYPE-64) groupId and version redundant when
executing archetype with parent
Posted by "Rod Coffin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-64?page=all ]
Rod Coffin updated ARCHETYPE-64:
--------------------------------
Attachment: ARCHETYPE-64-maven-archetype-core.patch
Test case and solution for issue
> groupId and version redundant when executing archetype with parent
> ------------------------------------------------------------------
>
> Key: ARCHETYPE-64
> URL: http://jira.codehaus.org/browse/ARCHETYPE-64
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Archetypes
> Affects Versions: 1.0-alpha-4
> Reporter: Rod Coffin
> Attachments: ARCHETYPE-64-maven-archetype-core.patch
>
>
> Running the archetype plugin in a parent project creates a sub-project (module). Although the parent elements are properly set in the child pom, the group id and version are repeated. These are not necessary since they will be inherited from the parent. Ex:
> <parent>
> <artifactId>parent</artifactId>
> <groupId>com.rfc.archetypes.example</groupId>
> <version>1.0-SNAPSHOT</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.rfc.archetypes.example</groupId>
> <artifactId>example-web</artifactId>
> <version>1.0-SNAPSHOT</version>
> Having this information is two places is bad in principle because it violates the DRY principle and in practice because they can get out of sync accidentally and it could be confusing.
--
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] Updated: (ARCHETYPE-64) groupId and version redundant when
executing archetype with parent
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/ARCHETYPE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated ARCHETYPE-64:
-----------------------------------
Component/s: (was: Archetypes)
Generator
Description:
Running the archetype plugin in a parent project creates a sub-project (module). Although the parent elements are properly set in the child pom, the group id and version are repeated. These are not necessary since they will be inherited from the parent. Ex:
{code:xml}
<parent>
<artifactId>parent</artifactId>
<groupId>com.rfc.archetypes.example</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>com.rfc.archetypes.example</groupId>
<artifactId>example-web</artifactId>
<version>1.0-SNAPSHOT</version>
{code}
Having this information is two places is bad in principle because it violates the DRY principle and in practice because they can get out of sync accidentally and it could be confusing.
was:
Running the archetype plugin in a parent project creates a sub-project (module). Although the parent elements are properly set in the child pom, the group id and version are repeated. These are not necessary since they will be inherited from the parent. Ex:
<parent>
<artifactId>parent</artifactId>
<groupId>com.rfc.archetypes.example</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>com.rfc.archetypes.example</groupId>
<artifactId>example-web</artifactId>
<version>1.0-SNAPSHOT</version>
Having this information is two places is bad in principle because it violates the DRY principle and in practice because they can get out of sync accidentally and it could be confusing.
> groupId and version redundant when executing archetype with parent
> ------------------------------------------------------------------
>
> Key: ARCHETYPE-64
> URL: http://jira.codehaus.org/browse/ARCHETYPE-64
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
> Affects Versions: 1.0-alpha-4
> Reporter: Rod Coffin
> Attachments: ARCHETYPE-64-maven-archetype-core.patch
>
>
> Running the archetype plugin in a parent project creates a sub-project (module). Although the parent elements are properly set in the child pom, the group id and version are repeated. These are not necessary since they will be inherited from the parent. Ex:
> {code:xml}
> <parent>
> <artifactId>parent</artifactId>
> <groupId>com.rfc.archetypes.example</groupId>
> <version>1.0-SNAPSHOT</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.rfc.archetypes.example</groupId>
> <artifactId>example-web</artifactId>
> <version>1.0-SNAPSHOT</version>
> {code}
> Having this information is two places is bad in principle because it violates the DRY principle and in practice because they can get out of sync accidentally and it could be confusing.
--
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