Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Sometimes I wanted to deploy, but I typed mvn package.

Sometimes I want to deploy to another alternative repository (using mvn deploy -DaltDeploymentRepository=...), immediately after the default deploy.

So I really don't want to package and test them again, because they are just succeeded. The result jars are just there, in the target/ directory. I hope I can deploy them.

I know there is deploy:deploy-file, but that's inconvenient to use, I don't want to specify groupId, artifactId again on the command line. It doesn't work for large project which contains a lot of jars to deploy, too.

share|improve this question

Use the maven.test.skip command line flag to skips tests:

mvn -Dmaven.test.skip=true install

Use the maven.repo.list command line flag to add another repository:

mvn -Dmaven.repo.list=
share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .