[GRADLE-2349] Upload to a remote repository with the maven plugin also installs into maven local Created: 13/Jun/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
The problem is that the maven ant tasks do this, not us.
We are behind a few patch revisions of the maven-ant-tasks jar, but I've checked and the latest still has this problem.
This is a problem for people who don't want their local maven repository filling up with this stuff, especially if they are using unique snapshots.
One option may be to inject a tmp dummy local repository and have the deployer use that.
|Comment by Hans Dockter [ 07/Aug/12 ]|
It would be interesting to know whether Aether exposes the same behaviour.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.