Personally I think we should just forge ahead. The upgrade from Java 5 to 6 is not nearly as severe as it was from 1.4 to 5. Additionally, much of the success of EJB 3.0, Seam and other modern frameworks can be attributed to the use of new language features such as annotations and generics. If you move forward, the users will too. When you hold back, you just condone the resistence to upgrade.<br>
<br>Granted, I tend to be progressive, but my feeling is, why not put your best foot forward?<br><br>-Dan<br><br><div class="gmail_quote">On Tue, Aug 18, 2009 at 1:11 PM, Pete Muir <span dir="ltr">&lt;<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>&gt;</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 all,<br>
<br>
I want to gather some feedback on whether everyone is happy if we make<br>
Java 6 a requirement for Web Beans. This will simplify the build<br>
slightly.<br>
<br>
JBoss 5.2 will require Java 6 (AFAIK), and I assume GlassFish will do<br>
as well.<br>
<br>
Anyone got strong opinions either way?<br>
<br>
Pete<br>
_______________________________________________<br>
webbeans-dev mailing list<br>
<a href="mailto:webbeans-dev@lists.jboss.org">webbeans-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/webbeans-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/webbeans-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://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br>