<p>Except releases would then no longer be 100% reproducible. Probably comes down to a matter of policy.</p>
<p>-Jordan</p>
<div class="gmail_quote">On Jan 28, 2011 6:33 PM, "Brian Leathem" <<a href="mailto:bleathem@gmail.com">bleathem@gmail.com</a>> wrote:<br type="attribution">> Good idea!<br>> <br>> Or something like either:<br>
> <version>[3.0.0.Beta2,3.0.1)</version><br>> or<br>> <version>[3.0.0.Beta2,3.1)</version><br>> <br>> That way breaking changes if bound to a version increment, would then <br>> require modules to re-release.<br>
> <br>> Brian<br>> <br>> On 01/28/2011 03:25 PM, Lincoln Baxter, III wrote:<br>>> Have we considered using version range specifiers via the maven <br>>> artifact syntax?<br>>><br>>> If modules used something like:<br>
>><br>>> <version>[3.0.0.Beta2,)</version><br>>><br>>> It would allow more flexibility as we go along / upgrade individual <br>>> modules. This way we wouldn't need to re-release *everything* when we <br>
>> re-release *one* thing. WDYT? I'm sure there are consequences, but <br>>> others may have ideas too.<br>>><br>>> ~Lincoln<br>> <br>> _______________________________________________<br>
> seam-dev mailing list<br>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>