Okay,
You need to add
> <releases>
> <enabled>false</enabled>
> </releases>
to the snapshot repo. I’ll add that to the README. This could be something I
mess up last year by deploying a release to snapshots by mistakes (I used to
have perl scripts to do it :-)).
With that added, mvn dependency:analyze shows that is picks up the 1.5.5
release. Failing that also make sure you’re using Maven 3. I’m pretty sure the
RELEASE also worked pre v 3. Also no harm in turning of snapshots from the
release repo.
> <repository>
> <id>ebi-repo</id>
>
> <url>http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/</url>
> <snapshots>
> <enabled>false</enabled>
> </snapshots>
> </repository>
> <repository>
> <id>ebi-repo-snapshots</id>
>
> <url>http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo-snapshots/</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> </repository>
J
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Cdk-user mailing list
Cdk-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdk-user
