>
> 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.
But that means I have to (manually?) build a release version for each
dependency used
.
>
>
> 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
That is exactly my Point. I dont wan't to have "pick latest version" in the
tag, just in the trunk.
I'll try to explain again what I'd wish to have. The pom in the Trunk of
Project B should contain:
<dependency>
<groupId>MyId</groupId>
<artifactId>A</artifactId>
<version>PICK THE LATEST</version>
</dependency>
If I release this today the tag created in source control should look like:
<dependency>
<groupId>MyId</groupId>
<artifactId>A</artifactId>
<version>2.4</version>
</dependency>
Releasing the same trunk tomorrow without any changes might lead to
<dependency>
<groupId>MyId</groupId>
<artifactId>A</artifactId>
<version>2.5</version>
</dependency>
If A has changed in the meantime. The tag version from today would still be
pointing to "2.4".
> 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.
Since i want the projects to pick up the latest build I would have to go
through the drudgery after
every commit. I mean this is what CI is all about: Every commit in Project A
does not only trigger
a build of Project A but does build all downstream Projects with the new
version of A to show
any integration problems.
You might wan't to look at ivys deliver task ant the replacedynamicref
attribute:
http://ant.apache.org/ivy/history/latest-release/use/deliver.html
Martin
>
> 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]
>
>
