[GRADLE-1726] Tooling API + M4 dependency resolution issues Created: 05/Aug/11  Updated: 28/Jul/13  Resolved: 28/Jul/13

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: Bug
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0

Attachments: File grails-data-mapping.log    

 Description   

Trying to import grails-data-mapping (from here: https://github.com/SpringSource/grails-data-mapping) into STS...

The project can be imported ok, but has problems building the 'full' eclipse model.
Construction of the model fails because it has trouble resolving a 'testRuntime' dependency on gemfire.

When we build the project on the commandline with 'gradle assemble' or 'gradle build'
(also using gradle M4 all the time) we get no such error.

It is also odd that this dependency should not resolve, since in the same log file that contains the error,
I see earlier on in the log that it already downloaded the pom and jar file that it can't seem to resolve later on.

Another odd tidbit of information. It seems that using Gradle M3 distribution from here:

http://repo.gradle.org/gradle/distributions/gradle-1.0-milestone-3-bin.zip

Sometimes works fine (no resolve error).

But on other occasions I've seen the M3 API fail to even construct the hierarchical model because of the resolution
error. I don't know why it sometimes works and sometimes doesn't (state of the cache maybe). At the moment, it seems to be working fine
with M3, but earlier I had more trouble with M3 (i.e. M4 API + M3 distro) than M4-distro on this project.

I have not personally verified, but my coleague reported he was able to work with these projects
using an older version of the STS plugin using M3 API + M3 distro and did not run into the resolving issue.

 Comments   
Comment by Peter Niederwieser [ 12/Aug/11 ]

gradle test gives me the same exception (with M4). From which repository is gemfire-6.5.1.4.jar supposed to be coming from?

Comment by Kris De Volder [ 15/Aug/11 ]

Hi Peter,

To be honest, I don't know. I'm picking at somewhat 'random' projects I find around the internet to test the Gradle STS tooling and reporting problems I encounter. I'm not really that familiar with the details of the builds.

I'll ask Burt Beckwith. He will probably be able to answer that question.

Kris

Comment by Burt Beckwith [ 15/Aug/11 ]

The dependency and repo are specified in https://github.com/SpringSource/grails-data-mapping/blob/master/grails-datastore-gemfire/build.gradle and when I removed the cached jar and re-ran a build from the commandline it downloaded them again:

:grails-datastore-gemfire:compileGroovy
Download http://dist.gemstone.com/maven/release/com/gemstone/gemfire/gemfire/6.5.1.4/gemfire-6.5.1.4.pom
Download http://dist.gemstone.com/maven/release/com/gemstone/gemfire/gemfire/6.5.1.4/gemfire-6.5.1.4.jar
Comment by Szczepan Faber [ 14/May/12 ]

With the latest gradle/STS I was able to import the project into Eclipse. After importing, certain projects have some errors I haven't dig through, fully. They seem like problems resolvable with the eclipse DSL.

Kris, can we close this issue as the dependency resolution problem has been fixed?

Comment by Adam Murdoch [ 23/Jul/13 ]

@Kris, can we close this issue, do you think?

Comment by Kris De Volder [ 24/Jul/13 ]

Sure. No point in keeping this open anymore.

Generated at Wed Jun 30 12:02:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.