I was intending to ask the exact same question since this is quite a
laborious task for us. Our project hierarchy is highly component
based, and as such, a bug fix release in a shared low-level component
can sometimes require ten to twenty releases of dependent projects.
The solutions I can see
oktober 2006 10:54
Till: Maven Users List
Ämne: Re: Managing Release Jars
I was intending to ask the exact same question since this is quite a
laborious task for us. Our project hierarchy is highly component
based, and as such, a bug fix release in a shared low-level component
can sometimes require ten
Hi Jonas,
On 31/10/06, Jonas Olsson [EMAIL PROTECTED] wrote:
Perhaps the original question is wrongly put, IMHO?
If you have a shared library it should only be included ONCE in the end
product, right?
And this inclusion should be of a specific version (to allow build
re-production), right?
Unless your projects are released in lock-step, you probably want to update
the dependency version manually. While this is labor intensive, it also
guarantees that you know exactly what you're building. As you analyze and
test against newer versions of the dependency, you can manage that small
