"Failed to validate POM" on transitive dependencies

[Ryan Nelson <rn...@Insight.com>]

I've got two projects that have a dependency: projA depends on projB.  I
build projB with no trouble, and it gets installed into my local
repository.  When I build projA I get this warning message:
 
"[WARNING] POM for 'projA:projA:pom:1.0-SNAPSHOT:compile' is invalid.
It will be ignored for artifact resolution.  Read: Failed to validate
POM."
 
This is a problem because projB may have transitive dependencies that
projA might need.
 
How can the POM validate fine when projB is built, but fail validation
when projA tries to include it?  I've examined the POM in the artifact
repo and it is, so far as I can tell, a perfectly valid POM.  Also, no
versions for the dependencies are specified in projB and projA ... both
get their version from the <dependencyManagement> sections in their
shared parent POMs.
 
I've seen this error posted in the user group before, but never seen a
good answer for it.  I've tried deleting the stuff in my local artifact
repo, etc.  Can someone point me in the right direction?
 
Thanks,
Ryan

RE: "Failed to validate POM" on transitive dependencies

[Ryan Nelson <rn...@Insight.com>]

I'm sorry, I botched the warning message in making substitutions.  The
message properly would read:

"[WARNING] POM for 'projB:projB:pom:1.0-SNAPSHOT:compile' is invalid. It
will be ignored for artifact resolution.  Read: Failed to validate POM."

In other words: projB's POM is failing validation during projA's build.

-----Original Message-----
From: Ryan Nelson [mailto:rnelson@insight.com] 
Sent: Tuesday, July 03, 2007 3:07 PM
To: users@maven.apache.org
Subject: "Failed to validate POM" on transitive dependencies

I've got two projects that have a dependency: projA depends on projB.  I
build projB with no trouble, and it gets installed into my local
repository.  When I build projA I get this warning message:
 
"[WARNING] POM for 'projA:projA:pom:1.0-SNAPSHOT:compile' is invalid.
It will be ignored for artifact resolution.  Read: Failed to validate
POM."
 
This is a problem because projB may have transitive dependencies that
projA might need.
 
How can the POM validate fine when projB is built, but fail validation
when projA tries to include it?  I've examined the POM in the artifact
repo and it is, so far as I can tell, a perfectly valid POM.  Also, no
versions for the dependencies are specified in projB and projA ... both
get their version from the <dependencyManagement> sections in their
shared parent POMs.
 
I've seen this error posted in the user group before, but never seen a
good answer for it.  I've tried deleting the stuff in my local artifact
repo, etc.  Can someone point me in the right direction?
 
Thanks,
Ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org