[GRADLE-3064] gradle-1-11 eclipse plugin not generating the project dependencies correctly Created: 08/Apr/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


When I updated to gradle1.11; see that the project dependencies being generated is different, and I think this causes eclipsePlugin to generate the .classpath.

This works fine in gradle-1-10

Here's the difference between the 2 versions.

[1]http://pastebin.com/7x0sGatw gradle-1-10
[2]http://pastebin.com/ueiG0p3h gradle-1-11 and above

As you can see, there is a wrong dependency being generated.

+--- project :src:common:common -> project :src:modules:discovery:container:common

Because of this is the classpathentry thats being generated by eclipse-plugin
<classpathentry kind="src" path="/discovery-container-common" exported="true"/> (Which is wrong, as it is making it think as if its dependent on the same project)

Not sure whether the "common" project name is creating this issue.. (this worked fine with gradle1.10 though)
[1] http://pastebin.com/7x0sGatw
[2] http://pastebin.com/ueiG0p3h

Comment by Gradle Forums [ 08/Apr/14 ]

I am not aware of any change between 1.10 and 1.11 that would cause this (yet). Can you attach `build.gradle` files where we can see what going on (simplified test case would be best). From your outputs I am wondering why there seems to be circular dependency
:src:modules:discovery:container:common ->
project :src:common:container:messaging ->
project :src:common:common ->
project :src:modules:discovery:container:common
where previously artifacts like com.canopi.cis:messaging:1406 were used.

Comment by Gradle Forums [ 08/Apr/14 ]

I checked in a scenario, where I was able to reproduce this issue.. This example pretty much mimics the issue I am having, when I use gradle-1.11

Please checkout this link. [1]https://github.com/vrvarma/gradle-dep...
[1] https://github.com/vrvarma/gradle-dependencies-issue

Comment by Radim Kubacki [ 08/Apr/14 ]

Simpler version of the problem:

include 'common', 'modules:common'


subprojects{ subproject->
   group = 'com.foo.acme'
   apply plugin:'java'


dependencies {
  compile project(':common')

Our dependency resolution cannot tell publication from :common to one from :modules:common because they have same project name and group.

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