[GRADLE-1258] Provide an init-repositories init script, which will initialize repositories according to their patterns, providing a clean repository deceleration outside of the build.gradle script Created: 19/Dec/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9-rc-3
Fix Version/s: None

Type: Improvement
Reporter: Tomer Cohen Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: Text File Added_default_repo-init_gradle_file_to_wrapper.patch     Text File Added_default_repo-init_gradle_file_to_wrapper1.patch    

Comment by Frederic Simon [ 19/Dec/10 ]

The goal is to externalize repositories declaration to a clean list of files managed inside the buildSrc directory.
By changing the gradlew, the starting experience is identical, and when using pure gradle adding "--init-script buildSrc/repo-init.gradle" will do the trick.
We are now using this layout for most of our project and it proved quite clean.
Furthermore it is possible to add:

apply from: buildSrc/repositories.gradle

in any gradle build file to have a clean import of the repositories declaration.

Comment by Justin Ryan [ 09/Feb/12 ]

This might be solved by the Init script improvements in m7, since you can put repositories.gradle in .gradle/init.d/. Though I'm waiting for an equivalent of init.d for gradlew.

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 11:50:58 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.