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 WendySmoak: http://wiki.apache.org/struts/StrutsMaintenanceMaven The comment on the change is: Updated instructions after changes in r417035 ------------------------------------------------------------------------------ == Building with Maven == === Local Install === - To build and install all of the artifacts (pom, jar, and war files) in your local Maven repository: + To build and install the framework artifacts (pom and jar files) in your local Maven repository: {{{ ~/svn/struts/current/action $ mvn @@ -43, +43 @@ $ mvn clean }}} + To build the example apps: + {{{ + $ mvn -P apps + or + $ cd apps + $ mvn + }}} + + === Binary and Source Assembly === - To build the -all assembly, enable the 'pre-assembly' profile (which produces the javadoc and source artifacts), and execute both 'install' and 'site': + 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 - $ mvn install site -P pre-assembly + $ mvn install site -P apps,itest,pre-assembly }}} And then create the assembly: {{{ @@ -57, +66 @@ The output will be in 'assembly/target/assembly/out'. - '''NOTE:''' The 'assembly:assembly' goal must be run from action/assembly. Somehow, this needs to be coordinated with release:prepare and release:perform, so that the assembly will contain the same jars that were just deployed to the repository. + '''NOTE:''' The 'assembly:assembly' goal must be run from action/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. @@ -65, +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 ''perform-itest'' profile is enabled. + Integration tests for Struts Action are located under the '''integration''' module. Integration tests will only be run if the ''itest'' profile is enabled. === Apps === The integration/apps-it module contains tests to confirm that each example app starts and displays its default page: {{{ ~/svn/struts/current/action/integration/apps-it - mvn -P perform-itest + mvn -P itest }}} In addition, each module inherits Cargo plugin configuration (from apps/pom.xml) which will start Tomcat 5.x and deploy the app: @@ -149, +158 @@ == Snapshots == - To deploy snapshots of all build artifacts (pom, jar, war, including -sources and -javadoc): + To deploy snapshots of all framework artifacts (pom and jar, including -sources and -javadoc): {{{ mvn deploy -P pre-assembly }}}
