I've always been of the opinion that snapshots are a bad idea for multi-module projects. It's a bit of a pain at first when you are maintaining all the modules, but as the teams diversify, it becomes a huge pain to get bitten by a broken snapshot and not understand why it broke or how to fix it. Much better is to depend on releases.<br>
<br>If you happen to be developing across modules, you will have a larger burden to coordinate the versions...but that is the trade-off to modularization. We already know monolithic builds eventually meet their doom.<br><br>
-Dan<br><br><div class="gmail_quote">On Sun, Nov 1, 2009 at 9:20 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys,<br>
<br>
I've switched us to a "no-snapshots" policy for Weld (both core and<br>
API). This helps improve the reliability of our builds, and makes it<br>
easier to do tagged builds (something Sun need in the run up to the<br>
GlassFish release). Currently this is only enforced manually, but I am<br>
looking at adding enforcing this to the build.<br>
<br>
Of course, you will still want to use snapshots locally (likely for<br>
the TCK). To do this, run with, for example: -Dcdi.tck.version=1.0.0-<br>
SNAPSHOT (other useful version properties are weld.api.version and<br>
jboss.interceptor.version).<br>
<br>
Pete<br>
_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>