[ 
http://issues.apache.org/struts/browse/STR-2899?page=comments#action_37968 ] 
            
Ted Husted commented on STR-2899:
---------------------------------

The current archtetype still references some WW configuration files. A zip of 
the layout being generated is annexed. 

Command: 
{code}
mvn archetype:create -DgroupId=com.myCompany.mySystem \
                       -DartifactId=myWebApp \
                       -DarchetypeGroupId=org.apache.struts \
                       -DarchetypeArtifactId=struts2-archetype-starter \
                       -DarchetypeVersion=1.0-SNAPSHOT \
                       
-DremoteRepositories=http://people.apache.org/maven-snapshot-repository
{code}

Personally, I find that infrastructure generated by the archetype includes too 
many optional elemens. We may want separte archetypes for Ajax and FTL-based 
applications. Otherwise, we should include an extensive readme, or link to a 
tutorial page that explains the various components that are being included. I 
fear that most people will end up deleting more than they would keep! 



 

> Add a Struts Blank Archetype for Maven 2
> ----------------------------------------
>
>                 Key: STR-2899
>                 URL: http://issues.apache.org/struts/browse/STR-2899
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Apps
>            Reporter: Wendy Smoak
>             Fix For: 1.x Next
>
>         Attachments: myWebApp.zip
>
>
> 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

        

Reply via email to