[
http://jira.codehaus.org/browse/MNG-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140259#action_140259
]
John Casey commented on MNG-3645:
---------------------------------
Actually, this error traces all the way back to the generated xpp3 parser,
which seems to be an issue of maven-model in 2.0.x being pegged to 1.0-alpha-8
of modello, where the rest of 2.0.x and 2.1 is currently on 1.0-alpha-18.
I'm investigating whether we can remove this exception for maven-model 2.0.x.
> Maven doesn't do strict model validation for POMs in the current reactor
> ------------------------------------------------------------------------
>
> Key: MNG-3645
> URL: http://jira.codehaus.org/browse/MNG-3645
> Project: Maven 2
> Issue Type: Bug
> Components: POM, Reactor and workspace
> Affects Versions: 2.0.9
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0.10
>
>
> For example, adding a dependencyManagement section like the following doesn't
> result in a parser/validation error:
> {code:xml}
> <dependencyManagement>
> <dependencies>
> <groupId>org.group</groupId>
> <artifactId>foo</artifactId>
> <version>1</version>
> </dependencies>
> </dependencyManagement>
> {code}
> Hint: It's missing the dependency element to contain the
> groupId/artifactId/version.
> This is probably a duplicate, but if so it looks like the original is buried
> somewhere deep...I can't find it.
--
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
