[GRADLE-1874] Tooling API: Avoid MissingPropertyException working with IntelliJ IDEA model Created: 27/Oct/11 Updated: 04/Jan/13 Resolved: 06/Dec/12 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Denis Zhdanov | Assignee: | Unassigned |
Resolution: | Not A Bug | Votes: | 0 |
Description |
Try to import spring security project - http://static.springsource.org/spring-security/site/build.html Result: |
Comments |
Comment by Szczepan Faber [ 16/Jan/12 ] |
This looks like a problem in one of the build files of the project, does the project build ok from the command line with the target gradle version you use in the tooling api? |
Comment by Denis Zhdanov [ 16/Jan/12 ] |
Checked that 'gradle build' for the project produces the same error but it works fine under 'gradlew build' (is configured to use milestone-3). |
Comment by Szczepan Faber [ 24/Jan/12 ] |
The target gradle version the tooling api uses should be the same as configured in wrapper. The presence of the wrapper pretty much means: "I'm compatible with this particular gradle version. With any other gradle version the build might fail." The tooling api by default is wrapper-aware. E.g. if you don't configure gradle installation in the GradleConnector, by default we will use the one configured by the wrapper. I'm inclined to resolve this issue unless there's anything else you find suspicious? |
Comment by Denis Zhdanov [ 24/Jan/12 ] |
So, am I right understanding that it is considered normal for particular build to be run successfully under the older gradle version and fail under the newer one? |
Comment by Szczepan Faber [ 26/Jan/12 ] |
Consider following scenarios:
Hope that helps! |
Comment by Denis Zhdanov [ 26/Jan/12 ] |
Ok, it's clear, thanks. |
Comment by Adam Murdoch [ 06/Dec/12 ] |
Hi Denis, can we close this issue now? |
Comment by Denis Zhdanov [ 06/Dec/12 ] |
yes |
Comment by Szczepan Faber [ 06/Dec/12 ] |
Fixed on JetGradle side, by supporting gradle wrapper. |