I would avoid version ranges, not only do they cause the described problem, the maven impl
However this is relatively easy to fix properly, when you release Seam, you release a BOM
with the updated Solder in, and recommend people use that. In this case the POM from Seam
XXX will be overridden and the updated Solder used.
On 28 Jan 2011, at 23:36, Jordan Ganoff wrote:
Except releases would then no longer be 100% reproducible. Probably
comes down to a matter of policy.
On Jan 28, 2011 6:33 PM, "Brian Leathem" <bleathem(a)gmail.com> wrote:
> Good idea!
> Or something like either:
> That way breaking changes if bound to a version increment, would then
> require modules to re-release.
> On 01/28/2011 03:25 PM, Lincoln Baxter, III wrote:
>> Have we considered using version range specifiers via the maven
>> artifact syntax?
>> If modules used something like:
>> It would allow more flexibility as we go along / upgrade individual
>> modules. This way we wouldn't need to re-release *everything* when we
>> re-release *one* thing. WDYT? I'm sure there are consequences, but
>> others may have ideas too.
> seam-dev mailing list
seam-dev mailing list