[MNG-3645] Maven doesn't do strict model validation for POMs in the current reactor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.5, 2.0.8, 2.0.9
• Fix Version/s: 2.0.10, 2.1.0
• Component/s: POM, Reactor and Workspace
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 02/Jul/08 13:14
• Updated: 26/Apr/10 12:30
• Resolved: 17/Dec/08 17:47

Description

For example, adding a dependencyManagement section like the following doesn't result in a parser/validation error:

<dependencyManagement>
  <dependencies>
    <groupId>org.group</groupId>
    <artifactId>foo</artifactId>
    <version>1</version>
  </dependencies>
</dependencyManagement>

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.

Issue Links

• is duplicated by: MNG-2747 Maven doesn't detect invalid dependency descriptions in the pom
• relates to: MNG-4019 Unrecognised association "exclude" in pom parsing <resource><directory><excludes> in 2.0.10-RC10
• relates to: MNG-3616 Null Pointer Exception when mirrorOf missing from mirror in settings.xml
• relates to: MNG-4644 Misplaced text contents in root element of POM is not rejected by parser
• supercedes: MNG-1678 missing element does not trigger any warning
• supercedes: MNG-2816 Pom without xsd import is not validated