struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Musachy Barroso <>
Subject Re: New Struts 2 Documentation Wiki - Next Step Improving Tutorials
Date Thu, 31 Dec 2009 00:06:36 GMT
I understand what you are saying and as I said previously I agree with
it. As for myself i always like to setup things by hand at least once
so I understand better how everything is related. From your tutorial
you can always link to the archetypes so anyone familiar with maven
and who doesn't want to go step by step can jump start. That should
not create any confusion I think.


On Wed, Dec 30, 2009 at 3:02 PM, phillips1021 <> wrote:
> Lukasz:
>   I appreciate your concern about not confusing users between the tutorials
> that use Maven and the Struts 2 Maven blank and other archetypes.
>   I think the Struts 2 blank Maven archetype is useful for experienced
> Struts 2 developers who use Maven.  But I don't think the Struts 2 Maven
> archetypes are useful for someone new to Struts 2.
>   Based on comments in the current Ready, Set, Go tutorial about the Struts
> 2 blank archetype and also that the archetype is not consistently available
> in the central repository, I think a beginner tutorial that shows a user how
> to setup a Struts 2 web application that uses Maven to manage the artifact
> dependencies would be very beneficial to people new to Struts 2.
>   Also having a Struts 2 Maven beginner's tutorial lets us build on that
> project for the other tutorials (e.g. Hello World, Using Tags, etc).  I'd
> like to see us have downloads (a Maven version and an Ant version) for those
> other tutorials.  So someone learning Struts 2 can read through our
> tutorials and download a complete example for each tutorial.
>   I think Struts 2 is a great web application framework and having easy to
> follow tutorials with complete examples readers can download helps us
> introduce Struts 2 to new users.  For someone new to Struts 2, the Struts 2
> Maven archetypes don't do that.  You have to already know Struts 2 to
> understand how to adapt the Struts 2 Maven archetypes to your specific
> project.  The Struts 2 Maven archetypes are good for experienced Struts 2
> developers who want to get a quick setup for a specific project (e.g Struts
> 2 portlet application).  Beginners need more hand-holding (e.g. here are the
> dependencies you need in pom.xml, struts.xml must be on the class path so
> put it in src/main/resources).
>   That said, I'll defer to the opinion of the majority of people on this
> list who are interested in the Struts 2 documentation online.  Many of you
> have much more experience then I do in introducing Struts 2 to new users.
> So I'd appreciate it if others could provide some feedback on this proposal.
> Bruce
> Lukasz Lenart wrote:
>> 2009/12/30 phillips1021 <>:
>>> Instead of just referring the user to the Maven Struts 2 blank archetype
>>> (which isn't available for last time I checked) I'd like to
>>> create a
>>> tutorial for how to setup a Struts 2 web application that uses Maven to
>>> manage artifact dependencies (what to put in the pom.xml, where to put
>>> struts.xml, how to include/configure Jetty to run the Struts 2 web
>>> application).  As part of the tutorial I'd like to have a zipped Maven
>>> project with these minimal configurations that the reader could download,
>>> unzip, and import into their own Maven-aware IDE.  I'm not sure where to
>>> host this zipped Maven project (I'm willing to put it on my own server).
>> I'm not sure regarding that part - it will duplicate what archetypes
>> are created for - it can be helpful for someone who don't know Maven
>> convention. We should push forward voting of archetypes - Christmas
>> time isn't the best time for any work ;-)
>> Regards
>> --
>> Lukasz
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> --
> View this message in context:
> Sent from the Struts - Dev mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message