[GRADLE-2980] publishToMavenLocal does not respect custom maven local home since 1.9 Created: 23/Dec/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.10
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Luke Daley
Resolution: Won't Fix Votes: 6

Known Issue Of:


I just moved from gradle 1.8 to gradle 1.10. Can it be that the publish maven plugin does not honor my local maven repository location setting (anymore)? The usual

gradle clean publishToMavenLocal

put the stuff in my home directory's .m2/ instead of the my local maven repository as stated in the default settings.xml (which of course is located in my home directory's -m2/)

I so far didn't find any migration issues for that part. (In fact I didn't see anything why Java developers should move away from 1.8, but my netbeans IDE kept whining about the 1.8 version of gradle for some reason)

Comment by Tom Kalmijn [ 08/May/14 ]

This bug can be reproduced with Gradle 1.11 on my machine (alas).

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:36:38 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.