[
http://jira.codehaus.org/browse/ARCHETYPE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raphaël Piéroni closed ARCHETYPE-186.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha-4
Fixed since revision 670687
> local archetype catalog not correctly updated
> ---------------------------------------------
>
> Key: ARCHETYPE-186
> URL: http://jira.codehaus.org/browse/ARCHETYPE-186
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 2.0-alpha-3
> Environment: Windows XP, java 1.5
> Reporter: Chris Graham
> Priority: Trivial
> Fix For: 2.0-alpha-4
>
>
> The archetype:update-local-catalog step is not correctly updating the
> archetype-catalog.xml file.
> It is taking the <name> element from the POM of the archetype and writing it
> as the <description> in the archetype-catalog.xml file.
> Shouldn't it be using the <description> element itself (if provided, which is
> is)?
> Eg, given this from the POM of the archetype:
> <name>Project Accelerator - Sample Project.</name>
> <description>WarpSpeed archetype for creating multi module project that
> has our EAR, EJB, WAR and Resource projects defined for us.</description>
> The archetype-catalog.xml file is written out as:
> <archetype>
> <groupId>au.com.warpspeed.archetypes</groupId>
> <artifactId>sample-project</artifactId>
> <version>1.0-SNAPSHOT</version>
> <description>Project Accelerator - Sample Project.</description>
> </archetype>
--
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
