[GRADLE-1057] Gradle should recognise external style dependency declarations which refer to a project in the same build and treat them as project dependencies Created: 28/Jul/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.8, 0.9 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Adam Murdoch | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Description |
|
For example: dependencies { compile group: 'mygroup', name: 'otherproject', version: '1.0-SNAPSHOT' }
Could be treated as dependencies { compile project(':otherproject') }
|
| Comments |
| Comment by Hans Dockter [ 28/Jul/10 ] |
|
This is an interesting one. It looks like a good solution to the many scenarios where you sometimes want to have a loosely coupled build and other times a more tightly one. This might depend on the role or snapshot vs. rb-branch, .... |
| Comment by Adam Murdoch [ 28/Jul/10 ] |
|
That's a good idea. |
| 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. |