Hi I've got a dozen projects or so with a <dependency> on a 1.0-SNAPSHOT artifact X ; recently, I've been using the maven release plugin for this artifact, so that I can release incremental versions with maven changes plugin jira changelogs, like 1.0.1, 1.0.2, and so on.
My problem is that each time I release a new artifact X (or even deploy a new SNAPSHOT), I have to upgrade the ~12 projects pom.xml in order to benefit from the latest upgrade. This is very cumbersome, and I'd like to have some automation enabled. I've tried setting the artifact X <version> to LATEST in my child projects so that the newest jar is always downloaded on mvn install, however, this does not seem to work, I'm getting the usual BUILD ERROR, saying 1) com.my.company.artifact:jar:LATEST is missing. - How is LATEST supposed to work, do I have to specify something in my artifact X pom.xml to say "I'm the latest version, too" ? Is it a repository "option" to tell which artifact is the latest one ? - How would you deal with such an upgrade situation where many projects rely on a single one, and this single one is evolving very often thru incremental releases ? Thanks if you shed some light :) laurent -- <a href="http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com - Mobile world, technology and more</a> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
