[GRADLE-1726] Tooling API + M4 dependency resolution issues Created: 05/Aug/11 Updated: 28/Jul/13 Resolved: 28/Jul/13
|Reporter:||Kris De Volder||Assignee:||Unassigned|
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.
When we build the project on the commandline with 'gradle assemble' or 'gradle build'
It is also odd that this dependency should not resolve, since in the same log file that contains the error,
Another odd tidbit of information. It seems that using Gradle M3 distribution from here:
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
I have not personally verified, but my coleague reported he was able to work with these projects
|Comment by Peter Niederwieser [ 12/Aug/11 ]|
gradle test gives me the same exception (with M4). From which repository is gemfire-184.108.40.206.jar supposed to be coming from?
|Comment by Kris De Volder [ 15/Aug/11 ]|
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.
|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/220.127.116.11/gemfire-18.104.22.168.pom Download http://dist.gemstone.com/maven/release/com/gemstone/gemfire/gemfire/22.214.171.124/gemfire-126.96.36.199.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.