Maven 2 & 3

Maven doesn't do strict model validation for POMs in the current reactor

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major 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
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

NOTE: This is not a problem in trunk / 2.1, probably because strict mode is always-on for projects build from the filesystem (i.e. not from a repository or local repository location).

Show
John Casey added a comment - NOTE: This is not a problem in trunk / 2.1, probably because strict mode is always-on for projects build from the filesystem (i.e. not from a repository or local repository location).
Hide
Permalink
John Casey added a comment -

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.

Show
John Casey added a comment - 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.
Hide
Permalink
John Casey added a comment -

Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

Show
John Casey added a comment - Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.
Hide
Permalink
Benjamin Bentmann added a comment -

Neither Maven 2.0.10-RC2, 2.1.0-M1 nor 3.0-SNAPSHOT are passing the corresponding IT. John, can you double check please?

Show
Benjamin Bentmann added a comment - Neither Maven 2.0.10-RC2, 2.1.0-M1 nor 3.0-SNAPSHOT are passing the corresponding IT. John, can you double check please?
Hide
Permalink
Brett Porter added a comment -

it was fixed by upgrading to alpha-18 + of modello (which is now on 2.0.10 and 2.1.0-M2)

Show
Brett Porter added a comment - it was fixed by upgrading to alpha-18 + of modello (which is now on 2.0.10 and 2.1.0-M2)

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.