Updated guidelines.<div><br></div><div><a href="http://seamframework.org/Seam3/DevelopmentGuidelines#H-MavenAndArtifactManagement">http://seamframework.org/Seam3/DevelopmentGuidelines#H-MavenAndArtifactManagement</a></div>
<div><br></div><div>-Dan<br><br><div class="gmail_quote">On Fri, Apr 16, 2010 at 1:09 PM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
All, whilst reviewing the Seam 3 pages, I noted that the recommendation was to use Maven 2.2. Actually, you should use Maven 2.0.10 if you want to be safe - the build should work with 2.2, but this is not guaranteed.<br>
<br>
You're probably wondering why we are still using Maven 2.0.10 - this is based on advice from the Maven team who recommend that if you don't need a feature from 2.1 or 2.2 (we don't) it's best to stick with 2.0.10 until Maven 3 is available.<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" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-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>
</div>