[MDEPLOY-26] Deploy to an interal repository, different from the one definied in the pom.xml

[jira-importer]

Geoffrey De Smet opened MDEPLOY-26 and commented

Use-case 1

I (not a developper) checkout Codehaus Mojo's jasperreports plugin and want to install it in my company remote repository.
The pom.xml is read-only of the jasperreports (because I might create patches later).

Use-case 2

I checkout spring-richclient and want to deploy the latest snapshot in my company remote repository.
However the configured repistory in the pom.xml is another one.
I cannot use the repo of spring-richclient, because they sometimes break backwards compability at the moment in their snapshots.

mvn deploy:deploy
will try to deploy it to the repository defined in the pom.xml
mvn deploy:deploy-file
is to much hassle with the exported pom, ..., especially in a multiproject
mvn deploy -DdeploymentRepository=scp://myInteralRepository
does not work, deploymentRepository is ignored.

A solution would be with
mvn deploy -DsomeParameter=scp://myInteralRepository

See also the user mailing list thread "mvn deploy external project to internal remote repository"

---

Affects: 2.1

Remote Links:

• GitHub Pull Request #231
  

[jira-importer]

John Dennis Casey commented

This is fixed, at least in SVN. I verified using the artifact resulting from the plugin's own build. The command I executed was:

mvn deploy:deploy-file -DrepositoryId=test \
    -Durl=file:///tmp/deploy-repo \
    -DrepositoryLayout=legacy \
    -Dfile=plugins/maven-deploy-plugin/target/maven-deploy-plugin-2.2.1-SNAPSHOT.jar \
    -DpomFile=plugins/maven-deploy-plugin/pom.xml \
    -DartifactId=test-artifact \
    -DgroupId=org.testGroup \
    -Dversion=1

If you want to use a standard Maven 2.x repository layout, simply leave out the -DrepositoryLayout property.