[MDEPLOY-25] deploy:deploy-file installs the file in the local repository too (but it should not do that)

[jira-importer]

Geoffrey De Smet opened MDEPLOY-25 and commented

deploy:deploy-file installs a jar in a remote repository, but currently also installs it in the local repository.
I believe this is a bug, because it makes you wrongly believe that the remote repository is ok when you run local tests afterwards.
If this is the desired behaviour, please notify it on the command line and the documentation of deploy:deploy-file

When I installed a simple hello.jar in my remote repository, I also found it in my local repository (in my user dir) after this command:

$ mvn deploy:deploy-file -Dfile=hello.jar -DgroupId=org.hello -DartifactId=hello -Dversion=0.7 -Dpackaging=jar -Dreposi
toryId=springRichclientRepository -Durl=file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repositor
y
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'deploy'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [deploy:deploy-file] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[INFO] [deploy:deploy-file]
Uploading: file:///D:/projects/sf/spring-richclient-mavenizer/pomResources/maven2repository/org/hello/hello/0.7/hello-0.
7.jar
6b uploaded
[INFO] Retrieving previous metadata from springRichclientRepository
[INFO] Uploading repository metadata for: 'artifact org.hello:hello'
[INFO] Retrieving previous metadata from springRichclientRepository
[INFO] Uploading project information for hello 0.7
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Sun Feb 19 19:38:12 CET 2006
[INFO] Final Memory: 2M/4M
[INFO] ------------------------------------------------------------------------

---

Affects: 2.1

Remote Links:

• GitHub Pull Request #260
  

[jira-importer]

John Dennis Casey commented

Deployment always implies installation in Maven. How does it make you wrongly believe the remote repository is alright? I'm not sure I follow...the whole point of this plugin is to write to the remote repository. Or, are you saying that you cannot verify what you put on the remote repository without first removing the locally installed artifact manually? If so, this is always the case in Maven. It's well documented in the lifecycle documentation here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

[jira-importer]

John Dennis Casey commented

see previous comment. this behavior is consistent with other deployment functions of Maven.

[jira-importer]

Geoffrey De Smet commented

fair enough, but could it deploy:deploy-file at least note that it's also installing it locally?

[jira-importer]

Geoffrey De Smet commented

(both in the documentation and in the logging output would be nice)

[jira-importer]

Brett Porter commented

let's add an option to disable it (default to how it is now), or at least document it.

[jira-importer]

Allan Q. Ramirez commented

Ok.. I 'll document it.

[jira-importer]

Allan Q. Ramirez commented

-added the document in the maven-site "guide-deploying-3rd-party-jars.apt"
-mentioned that the artifact would be installed both on local and remote repository