mvn –version
mvn install
mvn clean install
(remove any pre-built binaries and then install the artifact)
mvn jetty:run-exploded --from ROO GWT
mvn [plugin-name]:[command-name]
================================
mvn dependency:tree
mvn dependency:copy-dependencies
ROO
===
dependency add --groupId org.springframework.integration --artifactId spring-integration-file --version 2.0.0.RELEASE
perform package
dependency remove --groupId org.springframework.integration --artifactId spring-integration-file --version 2.0.0.RELEASE
perform command --mavenCommand install
Phase Description
validate Runs a sanity check on the project itself
compile Compiles source code
test Runs the compiled test classes (delegating to a particular unit testing plugin runner, like jUnit or TestNG)
package Produces an artifact from the compiled code and classpath resources and stores it in the target folder, at the root of the project
integration-test Process and deploy the packaged artifact into an integration testing environment
verify Run checks to confirm that the package is valid
install Installs the packaged artifact in your local repository. Your local repository is a folder where all the downloaded dependencies are kept and cached. Subsequent builds that try to resolve a dependency already in the cache will not redownload the dependency, instead using the one in the local repository. Normally, it's in your home directory, under .m2, in a folder called repository. Thus, on my system, this would be /home/jlong/.m2/repository
deploy Copies the final artifact to another environment. Typically, a shared server so that different teams can share a shared dependency.
No comments:
Post a Comment