[
http://jira.codehaus.org/browse/MNG-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194342#action_194342
]
Paul Benedict commented on MNG-4390:
------------------------------------
If a developer is sharing settings.xml among the same minor versions (2.1, 2.2,
etc.), this is reasonable, but if this change then facilitates sharing across
major versions (2.1, 3.0), then I think it's not the correct approach. I hope
the latter requires an XSD or something to prevent this.
> Make parsing of settings.xml lenient with respect to unrecognized tags
> ----------------------------------------------------------------------
>
> Key: MNG-4390
> URL: http://jira.codehaus.org/browse/MNG-4390
> Project: Maven 2
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.x
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> Currently, Maven parses the settings.xml in strict mode, making it error out
> upon occurrence of any tag that it does not understand. This makes
> co-existence of different Maven versions on the same machine more difficult
> as a user employing some newly added settings elements can't use the same
> settings.xml for old Maven versions.
> In principle, unrecognized elements don't hurt and can be safely ignored. The
> only benefit from the strict parsing is to tell the user about potential
> problems/typos in his settings.xml. This can however also be realized by
> warnings instead of errors.
--
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
