On Nov 23, 2007 9:07 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > This worked: > mvn archetype:create -DgroupId=tutorial -DartifactId=tutorial > -DarchetypeGroupId=org.apache.struts > -DarchetypeArtifactId=struts2-archetype-starter > -DarchetypeVersion=2.0.11 > -DremoteRepositories=http://people.apache.org/builds/struts/m2-staging-repository
Thanks! That did it! As to > * struts2-archetype-starter - Creates a starter Struts 2 app First, this looks excellent! Though, I'd like to suggest/commit four minor changes * In struts.xml, rename "myPackage" to "my-package" for consistency with the "struts-default" naming style. * Rename the "jsp" folder "results". * Remove "default.jsp" from the list of welcome files, leaving "index.jsp" and "index.html". * Roll the struts.properties file into the struts.xml. Other tweaks: Overall, I'd like to consider the struts.properties alternative deprecated, otherwise we end up with three approaches to configuration (which is at least one too many!) Since we can use annotation for type converters, I'd also suggest we drop the dummy xwork-conversion.properties file. If we want to bundle log4j with this, that's fine with me, but let's actually use it. I'd rather that there were no unnecessary files in the archetype. On the same not, is the DWR configuration needed for the (so-called) client-side validation? If its needed, how do we feel about using a beta here? Did we mean to drop the messages resources? (Which is fine, we have them in the MailReader.) Personally, I'm not a fan of a separate "resources" folder. It seems easier to put those files at the java source root, so that related members are closer together (separate by concern, not by species). But I realize it's one of those things that other people seem to like. :) Personally, I also like to name the applicatonContext.xml "spring.xml" (call a bowl, a bowl). But, again, I know that's not the Spring default convention. mvn jetty:run turned up a 404 for me. But, I was also having some issues with AppFuse and jetty:run, so maybe it's just me. I got it up and running under MyEclipse without difficulty. I like that we included a sitemesh layout. The sidebar links don't work for me, but I suppose that's because I'm suppose to fill something in someplace. (Unless it's just broken.) Since I don't know what to put where to fix or finish it, I suddenly feel like I'm too stupid to use Struts 2 :) At one point, we were trying to align the bootstrap tutorial with the archetype. If we had an "starter" tutorial that explained how to change the sitemesh setup, and how to inject a Spring bean, and maybe how to create a logging statement, I think we'd be good to go. I could do the Spring part, but I could use a leg-up on our SiteMesh configuration. Once this vote passes, for 2.1, I'd like to rename the blank application to "starter" and make it a checked-in, initialized version of what the archetype outputs, so that we don't have two codebases to maintain. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
