Why must set version?

[jiangshachina <ji...@gmail.com>]

Hi guys,
I encounter a very strange problem.
I have two pom.xml(represented as A and B), B extends A;
the packaging of A is pom, the packaging of B is jar.
I add many artifacts to A as dependency management, and add some of them to
B as real dependencies.

I use following pattern statements in A,
<dependencyManagement>
  <dependency>
    <groupId>org.apache.ws.commons.axiom</groupId>
    <artifactId>axiom-api</artifactId>
    <version>1.1.1</version>
  </dependency>
</dependencyManagement>
and use the following pattern statements in B,
<dependencies>
  <dependency>
    <groupId>org.apache.ws.commons.axiom</groupId>
    <artifactId>axiom-api</artifactId>
  </dependency>
<dependencies>
Then when I package project B, then an error thrown.
The error said version is missed.
I find that the matter just happen on artifacts in group
org.apache.ws.commons.axiom.
That's why?!

a cup of Java, cheers!
Sha Jiang
-- 
View this message in context: http://www.nabble.com/Why-must-set-version--tf2650547s177.html#a7396705
Sent from the Maven - Users mailing list archive at Nabble.com.


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