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" <firstname.lastname@example.org
> 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