[
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
