You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2010/10/04 00:31:32 UTC
[jira] Closed: (ARCHETYPE-282) When reading the
archetype-metadata.xml file, would be helpful to know if the XML was badly
formed
[ http://jira.codehaus.org/browse/ARCHETYPE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed ARCHETYPE-282.
-----------------------------------
Resolution: Fixed
Assignee: Herve Boutemy
code simplification done in r1004061
> When reading the archetype-metadata.xml file, would be helpful to know if the XML was badly formed
> --------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-282
> URL: http://jira.codehaus.org/browse/ARCHETYPE-282
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
> Affects Versions: 2.0-alpha-4
> Environment: Windows, but affects all envs
> Reporter: Chris Melikian
> Assignee: Herve Boutemy
> Priority: Minor
> Fix For: 2.0
>
> Attachments: DefaultArchetypeArtifactManager.java.patch
>
>
> If archetype-metadata.xml is malformed, say with a module element which is unclosed (missing slash), there is no error message displayed in the log output, even with the debug(-X) parameter set.
> The DefaultArchetypeArtifactManager class contains methods which catch exceptions but do not log the problem. The problem is just silently ignored. I've created a patch file to log the problem at WARN level so that anyone who has a problem can see why it occured.
--
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