[GRADLE-1494] Tooling api skeletal project tries to download dependencies Created: 26/Apr/11  Updated: 04/Jan/13  Resolved: 04/May/11

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

Type: Bug
Reporter: Adam Murdoch Assignee: Szczepan Faber
Resolution: Fixed Votes: 0


To reproduce, change the tooling api 'model' sample to point to the root of the gradle source tree. Should blow up with a 'missing dependency' exception, complaining that 'coreImpl' cannot be found.

Comment by Szczepan Faber [ 28/Apr/11 ]

I cannot seem to reproduce it. With milestone-3 and with latest snapshot build from head today the eclipse model builds ok for the gradle project (I was using the model sample).

Later I will try to write an automated test that builds model for gradle project itself.

Comment by Adam Murdoch [ 29/Apr/11 ]

Sorry. Turns out there was one other change I made to the sample. It's fetching a HierarchicalEclipseProject (ie the minimal model), rather than an EclipseProject (ie the full model). Fetching the full model is working, fetching the minimal model is failing.

Comment by Szczepan Faber [ 30/Apr/11 ]

I was able to reproduce the misbehavior of building of the minimal model (btw. since we always call the HierarchicalEclipseProject the 'minimal model', shouldn't it simply be called MinimalModel?). I fixed that, yet the misbehavior I faced was slightly different than your original description. The build failed for me with 'unresolved dependency' and the bugfix was about making sure we don't resolve jar dependencies when building the MinimalModel. Is this what you wanted to fix with this ticket?

Comment by Szczepan Faber [ 12/May/11 ]

The fix is available in one of the latest snapshots. For example you can update your gradle-wrapper.properties:


Generated at Wed Jun 30 11:56:56 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.