I believe maven/pom.xml is the parent of core/pom.xml, and in this
parent pom.xml you have:
<lucene.version>2.9.0</lucene.version>
and
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers</artifactId>
<version>${lucene.version}</version>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-core</artifactId>
<version>${lucene.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
So this then sets the version of Lucene to be 2.9.0 for all children
pom files.
-- Ken
On Oct 27, 2009, at 3:29pm, Adil Aijaz wrote:
Hi there
In core/pom.xml there is no version tag for:
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-analyzers</artifactId>
</dependency>
<dependency>
<groupId>org.apache.lucene</groupId>
<artifactId>lucene-core</artifactId>
</dependency>
my experience with maven is fairly limited. So, my question is:
1) How does maven resolve to look for 2.9.0-SNAPSHOT version for
these two artifacts? Note that I only have the maven trunk checked
out. I do not have the lucene project checked out.
2) Of course 2.9.0-SNAPSHOT artifacts do not exist in the central
repository. So the build fails. I have to explicitly add the version
tag for 2.9.0. Is there a way to avoid the build failure without
adding version tags?
Adil
--------------------------
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-210-6378
