mirror of
https://github.com/ohmyzsh/ohmyzsh.git
synced 2024-11-22 22:00:08 +00:00
745b6550a6
The problem that can occur is ocassionally mvnw will not be executable. This can happen if mvnw is included from an archetype, as unix permissions aren't preserved within the jar they're stored in. Only using mvnw if it exists AND is executable |
||
---|---|---|
.. | ||
mvn.plugin.zsh | ||
README.md |
Introduction
The mvn plugin provides many
useful aliases as well as completion for the mvn
command.
Enable it by adding mvn
to the plugins array in your zshrc file:
plugins=(... mvn)
Aliases
Alias | Command |
---|---|
mvncie |
mvn clean install eclipse:eclipse |
mvnci |
mvn clean install |
mvncist |
mvn clean install -DskipTests |
mvncisto |
mvn clean install -DskipTests --offline |
mvne |
mvn eclipse:eclipse |
mvncv |
mvn clean verify |
mvnd |
mvn deploy |
mvnp |
mvn package |
mvnc |
mvn clean |
mvncom |
mvn compile |
mvnct |
mvn clean test |
mvnt |
mvn test |
mvnag |
mvn archetype:generate |
mvn-updates |
mvn versions:display-dependency-updates |
mvntc7 |
mvn tomcat7:run |
mvnjetty |
mvn jetty:run |
mvndt |
mvn dependency:tree |
mvns |
mvn site |
mvnsrc |
mvn dependency:sources |
mvndocs |
mvn dependency:resolve -Dclassifier=javadoc |