<p>Agreed. </p>
<p>Lincoln Baxter III<br>
<a href="http://ocpsoft.com">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com">http://scrumshark.com</a><br>
Keep it simple.</p>
<p><blockquote type="cite">On Dec 10, 2009 3:43 PM, "Dan Allen" <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br><br>Overall, the new home page looks great. However, I'm not comfortable with the "Getting started" section. We are sending them on a wild goose chase right away to Wikipedia, which wrongly identifies Tomcat as a Java EE Application Server, which it is absolutely not (sorry, I get worked up over that topic).<br>
<br>I think what we need to do is direct them straight to the getting started page which provides a Maven 2 archetype to deploy either to Jetty/Tomcat or a Java EE app server (GlassFish is probably going to be the most neutral recommendation given it is the RI). We may have to tinker with our options here. It really is more complex than it should be right now.<br>
<br>I'd like to recommend using the Maven 2 archetypes that Steven Boscarine has been preparing in the Weld source tree. Keep in mind that there is no hard dependency to Weld, except for the use of the Weld servlet extension to use CDI on Tomcat and Jetty. The Java EE 6 archetype, on the other hand, creates a project that produces a pure, server-independent WAR based on JSF 2.0, BV 1.0 and CDI 1.0. The only tie to Weld is an import of the helper POM that sets the API versions in a dependency management section (just a convenience thing). We are working to get these things published to Maven central. Again, more details to come.<p>
<font color="#500050">
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux ...</font></p></blockquote></p>