[GRADLE-3322] Changed behaviour of Dependency Resolve Rules when replacing a project dependency with a dependency on the same module version Created: 15/Jul/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Known Issue Of:
2.5

 Description   

https://discuss.gradle.org/t/gradle-2-5-changed-behaviour-of-dependency-resolve-rules-when-replacing-a-project-dependency-with-a-dependency-on-the-same-module-version/10609/4

The changed behaviour occurs when a dependency resolve rule is used on a Project dependency, and the 'useVersion()' or 'useTarget()' method supplies the exact coordinates of the depended-on project. In that case, Gradle <= 2.4 will leave the project dependency intact, whereas Gradle 2.5 will replace the project dependency with an external dependency.

If the 'useTarget()' or 'useVersion()' methods are used on a project dependency and provide different coordinates to the depended-on project, then the project dependency will be replaced by an external dependency, in all versions of Gradle.

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