My experience here is also limited. I think it is desirable in any event to explicitly specify a version here.
But the latest version is 2.9.0, and i assume it goes for that, so that's why it happens to work? I don't get a build failure, but, I am using version 0.2, which is all but released now. I remember explicitly removing references to 2.9.0-SNAPSHOT which might also do it. So, probably best to try the latest from Subversion and see if you see any issues? On Tue, Oct 27, 2009 at 10:29 PM, Adil Aijaz <[email protected]> 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 > >
