[ http://jira.codehaus.org/browse/MNG-252?page=all ]
John Casey resolved MNG-252:
----------------------------
Resolution: Fixed
added code to read in a pom as a string, do an indexOf("modelVersion") to
decide whether it's a v3 or v4 pom...since m1 didn't do checking for extraneous
elements, I suppose someone could still throw a monkeywrench into the works by
declaring this element in a m1 pom, but it should recover and skip the artifact.
Should be fixed.
> allow repoclean converter to read from a repository containing both v3 and v4
> poms, and convert each correctly
> --------------------------------------------------------------------------------------------------------------
>
> Key: MNG-252
> URL: http://jira.codehaus.org/browse/MNG-252
> Project: m2
> Type: Improvement
> Components: repository-tools
> Environment: all
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-alpha-2
>
>
> currently there is no reliable way to detect whether a given POM is a v3 pom
> (from maven1) or a v4 pom (from maven2-alpha-0+). This makes it impossible to
> look at *.pom and decide which conversions to use in validating and/or
> cleaning the POM, and moreover which libraries to use in reading the file
> (they are separate Xpp3Reader implementations).
> It would be good to be able to sort out a repository that currently contains
> both maven1- and maven2-produced artifacts, and normalize them into maven2
> format.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
