Package and Deploy
From Taylor
Contents |
[edit]
Version Control
Check in the model, diagrams, and generated code and descriptors into your version control system. It is typical to generate the code, then tweak it enough to compile, and then check it in. Then do any major modifications and check that in before iterating again through the model and regenerating.
[edit]
Build
- Change directories to your master project and run mvn clean install to clean, compile, test, package, and install all the sub-projects: jpa, ejb, jsf, web, app, qa, doc, etc.
[edit]
QA Test
- Change directories to your qa project and run mvn clean install -Ptest
- This will download and install JBoss server under the target directory
- Then start the server using Cargo and run the JSFUnit tests
[edit]
Deploy
- The App project's pom.xml has the logic to copy the Ear file to your JBoss server.
- First, copy the downloaded jboss server from your qa target directory to C:\jboss-4.2.3.GA
- Setup the JBOSS_HOME system property to point to your JBoss installation
- SET JBOSS_HOME=C:\jboss-4.2.3.GA
- Change directories to your app project and run mvn clean install -Pdev
- This will copy the new Ear to the JBOSS_HOME/server/all/deploy
[edit]
Packaging
- Run mvn site to generate the project website with javadoc, xref, and test reports.
- Optional: mvn site dashboard:persist dashboard:dashboard site:deploy
- Run mvn assembly:assembly to package everything into zip and tar files.
- Make these modifications to support this.
[edit]
Other Useful Maven Plugins
[edit]
Reports
- http://maven.apache.org/plugins/maven-pmd-plugin/
- http://maven.apache.org/plugins/maven-changelog-plugin/
- http://maven.apache.org/plugins/maven-changes-plugin/
- Maven Site Gen Tutorial
[edit]

