Maven uses the notion of a build life-cycle to which plugins can attach. Plugins are similar to Ant tasks. When a Maven build is invoked, we specify a point in the life-cycle up to which the build should proceed. The compile phase comes before test, and test comes before package, and package comes before install. Once we have Maven setup, we can invoke the Struts build, and specify which phase the build should use.
Running mvn in source root will download and setup dependency jars in ~/.m2/repository.
$ mvn
$ mvn -Pprofile1,profile2,profile3
Zsh/Bash/Emacs/Vim/Grep/Sed/Awk/Javac...
$ sh deps/install-non-oss.sh $ mvn -Dnonoss install $ ant debug # Good ol' way of doing things
FIXME: Add on how to use IntelliJ IDEA with CS, building, debugging, editing, git checkouts
FIXME: Add on how to use Eclipse with CS, building, debugging, editing, git checkouts
$ mvn -o -Pextras,plugins,xwork
// Bash export MAVEN_OPTS=-Xmx512m // Windows set MAVEN_OPTS=-Xmx512m