[MNG-4491] Maven3 reports warnings about POM problems in very spurious way

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.0-alpha-5
• Component/s: Errors
• Assignee: Benjamin Bentmann
• Reporter: Tamas Cservenak
• Created: 12/Dec/09 07:58
• Updated: 17/Sep/10 16:55
• Resolved: 17/Sep/10 16:55

Description

In relation to issue MNG-4490, Maven3 reported the following on CLI:

[WARNING] Invalid artifact metadata for org.sonatype.nexus:nexus-proxy:jar:1.4.1-SNAPSHOT, transitive dependencies (if any) will not be available, enable debug logging for more details

This is due to the issue above (the branch i worked on completely revamped the dependencies in aggregator poms, hence the module pom became "invalid", since it contained dependencies that would be "filled in" from dependency management section, but they were not, hence by Maven3 they were considered "invalid").

What I was thinking, that maybe we should distinguish between "corrupt" POMs in way like:

• syntactical broken, which is like unparseable POM (usually corrupted during transport or proxy issues)

• semantically broken – this is what Maven3 tried to tell me – a POM that was not "correct" in validation sense (in this case, depepndency had no "version" declared)