[GRADLE-3219] ~/.m2/settings.xml is parsed for every project in a multi-project Gradle build Created: 28/Dec/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

In a multi-project build `repositories` clause needs to be defined for every project - either with `allprojects` or via `init.gradle`. If the local Maven repo is defined as one of the repositories, the method `getLocalMavenRepository` of `DefaultLocalMavenRepositoryLocator` is called every time a new subproject is parsed. In case repositories are defined for the buildscript of subprojects as well, this method is called 2N times where N is the number of projects. Every time this method is called it parses the `~/.m2/settings.xml` file and checks whether there is an override of the default repository location.
Ideally should be done only once - no reason there should be N (or worse, 2N) instances of the repository object. This is true for every repository, but the initialization of the local repo is the most costly.

 Comments   
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:43:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.