I recommend "1.0.1", as I dislike ranges (might break reproducible builds
and is just to much automagic in my taste).
"RELEASE", "LATEST" is depracted and should not be used.
When ever a new release is available you need to update the bar pom.
Or, you could keep both projects together with an aggregating project and
have one release lifecycle for them (same version in both,
"${project.version}").
/Anders
On Tue, Jan 4, 2011 at 11:46, Leon Rosenberg <rosenberg.l...@gmail.com>wrote:
> Hi,
>
> say I have two projects,
> foo and bar, and bar depends on foo. My question is how should I
> properly declare this dependency.
> From the maintainers point of view (and I'm the maintainer of both) I
> always want bar to use the newest release of foo.
> So, I have a released version of foo - 1.0.1, which is known to me at
> the moment I'm writing the pom for bar.
> Do I reference foo in bar as:
>
> 1.0.1
> or
> [1.0.1,)
> or
> [1.0.1]
> or
> RELEASE
> or
> ... ?
>
> regards
> Leon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
