[ http://issues.apache.org/struts/browse/WW-1412?page=comments#action_38237 ] Ted Husted commented on WW-1412: --------------------------------
I'd like to align the archetype (whatever it is called) with the new "bootstrap" tutorial code, which is the direction of the current struts-blank application. The application uses an "example" package for any bundled goodies. The tutorial talks about a "tutorial" packlage. The idea would be that someone could create a new application based on either a WAR or an archetype, and start adding the tutorial code in a new "tutorial" package. In the end, the tutorial package would match the example package, included with the WAR or archetype. Ideally, if there is something that we want to offer in the archetype, then there should be corresponding coverage in the tutorial, to help people get started with the example configuration. Right now, the starter archetype might create as many questions as it answers, given all the configuration files that are included. I'm not saying that's a bad way to go, but I am saying we need to explain the archetype better, if it is going to serve its intended purpose. We also need to be careful about what we enable in the archetype. For example, in the Starter archetype, the Spring configuration instantiates an Action, just as an example. If the example class is deleted, Spring fails fast. Whatever sample code we do provide should be easy and harmless to delete. Also, in the starter archetype POM, we include JSP 2.0 as a dependency. Why is that? We don't seem to need it for the showcase. One side-effect is that some 2.3 taglibs (like the Struts 1.3 taglib) may not work with JSP 2.0 on board. My general concern is that by enabling every conceivable option in the archetype, we may be making it harder for people to get a quick start on a new application, rather than easier. -Ted. > Conform Maven Archetype and Blank application > --------------------------------------------- > > Key: WW-1412 > URL: http://issues.apache.org/struts/browse/WW-1412 > Project: Struts 2 > Issue Type: Task > Components: Misc > Reporter: Wendy Smoak > Fix For: 2.0.1 > > > Bring the struts-archetype-blank module out of the sandbox to > struts/maven/trunk/. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
