RELEASE is deprecated, and AFAIK only ever worked for plugins On 05/03/2009, B Smith-Mannschott <[email protected]> wrote: > On Thu, Mar 5, 2009 at 08:15, Martin Eigenbrodt > <[email protected]> wrote: >> Thanks for your response Ben, >> I've considered this workaround, but I need a way to always pick the >> latest >> build of a dependend project. I know there are >> "SNAPSHOT" Builds but those break the paradigm "a revision never changes". >> Even if I used snapshot build, for each release I would have to pull a >> release for each dependency to get a "Snapshot Free" release. Or is this >> done automatically by the release plugin? >> >> Martin > > The release plugin *is* clever enough to ask you if you want to > replace SNAPSHOT versions in your dependencies with real release > versions. Once it's gotten the necessary information from you, it > makes the edits on your behalf. A good feature, that. > > The problem with "always picking the latest build" is that you won't > know anymore which that was when you check out a two-month old tag > form source control and try to repeat the build. I too have projects > where I want my dependencies to always go to the latest build. I just > go through the drudgery of updating users when such a library has a > new release. > > Speaking of releases, I read something in Sonatype's Maven book about > using RELEASE as the version for a dependency. Supposedly this will > always take the newest released version (SNAPSHOTs are not > considered). It hasn't worked for me (mvn 2.0.9), I assume this > feature will come along in the next version. > > // ben > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
