You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@struts.apache.org by Apache Wiki <wi...@apache.org> on 2006/07/11 22:00:08 UTC

[Struts Wiki] Update of "StrutsMaintenanceMaven" by TedHusted

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.

The following page has been changed by TedHusted:
http://wiki.apache.org/struts/StrutsMaintenanceMaven

The comment on the change is:
Update paths

------------------------------------------------------------------------------
  
  == Maven Setup ==
  
- Download and install Maven 2 from http://maven.apache.org.
+ Download and install Maven 2 from http://maven.apache.org/.
  
  Maven 2 does not use .properties files.  Per-developer and per-system configuration is done in '''~/.m2/settings.xml'''.  (Where '~' represents the user's home directory.)  For more information, refer to the [http://maven.apache.org/maven-settings/settings.html settings model] and the Suggested Settings section below.
  
@@ -16, +16 @@

  
  The Struts Subversion repository is organized into sub-projects.  You can check out Struts Action 1 alone using this URL:
  {{{
-    svn co https://svn.apache.org/repos/asf/struts/action/trunk  action
+    svn co https://svn.apache.org/repos/asf/struts/struts1/trunk struts1
  }}}
  Or you can check out all of the sub-projects, including the sandbox, with this:
  {{{
-    svn co https://svn.apache.org/repos/asf/struts/current  current
+    svn co https://svn.apache.org/repos/asf/struts/current current
  }}}
  
  === Snapshot or Distribution ===
  
- The following instructions should work equally well from the 'src' directory of a Struts Action snapshot or distribution.  If they don't, let us know!
+ The following instructions should work equally well from the 'src' directory of a Struts snapshot or distribution.  If they don't, let us know!
  
  == Building with Maven ==
  
  === Local Install ===
  To build and install the framework artifacts (pom and jar files) in your local Maven repository:
  {{{
-    ~/svn/struts/current/action
+    ~/svn/struts/current/struts1
     $ mvn
  }}}
  
- (The default goal, configured in action/pom.xml is '''install'''.)
+ (The default goal, configured in struts1/pom.xml is '''install'''.)
  
  To clean up, which will delete all of the 'target' directories:
  {{{
@@ -55, +55 @@

  === Binary and Source Assembly ===
  To build the assemblies, enable the 'pre-assembly' profile (which produces the javadoc and source artifacts) as well as 'itest' and 'apps', and execute both 'install' and 'site':
  {{{
-    ~/svn/struts/current/action
+    ~/svn/struts/current/struts1
     $ mvn install site -P apps,itest,pre-assembly
  }}}
  And then create the assembly:
  {{{
-    ~/svn/struts/current/action/assembly
+    ~/svn/struts/current/struts1/assembly
     $ mvn assembly:assembly
  }}}
  
  The output will be in 'assembly/target/assembly/out'.
  
- '''NOTE:''' The 'assembly:assembly' goal must be run from action/assembly.
+ '''NOTE:''' The 'assembly:assembly' goal must be run from struts1/assembly.
  
  In [http://www.nabble.com/Re%3A-building-assemblies-from-the-top-level-project-directory-p4735063.html this post], John Casey explains why 'mvn assembly:assembly' is a separate command with Maven 2.0.
  
@@ -74, +74 @@

  
  The Maven 2 [http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html build lifecycle] includes a phase for integration testing.  See [http://jira.codehaus.org/browse/MNG-1381 MNG-1381] and the [http://docs.codehaus.org/display/MAVEN/Testing+Strategies Testing Strategies] wiki page for more information.
  
- Integration tests for Struts Action are located under the '''integration''' module.  Integration tests will only be run if the ''itest'' profile is enabled.
+ Integration tests for Struts 1 are located under the '''integration''' module.  Integration tests will only be run if the ''itest'' profile is enabled.
  
  === Apps ===
  
@@ -199, +199 @@

  
  == TODO ==
  
-  * Consolidate some of the example apps to reduce the size of the distribution (?Suggested by Don?)
+  * Consolidate the Examples application into the new Cookbook to reduce the size of the distribution 
   * Create a custom deployment plugin to handle promoting our test builds from cvs.apache.org/maven-snapshot-repository to www.apache.org/dist/maven-repository.
    * http://www.nabble.com/Re%3A-m2-Releases-and-test-builds-p3824610.html
   * Figure out how to run the Cactus tests in 'sandbox/apps-test/el-it' against the strutsel-exercise-taglib webapp which is in the 'apps' module.