Dynamic properties are deprecated
While running the multiproject-all-conventions. I received this error with Gradle 1.1 on Windows 7
Dynamic properties are deprecated:
http://gradle.org/docs/current/dsl/org.gradle.api.plugins.ExtraProp...
Deprecated dynamic property: "type" on
"DefaultExternalModuleDependency{group='org.graniteds',
name='granite-swc', version='2.2.0.SP1', configuration='default'}",
value: "swc".
Deprecated dynamic property "type" created in multiple
locations.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Yennick Trevels on 11 Sep, 2012 03:28 PM
Hi Jim,
Thanks for reporting this issue. It's caused by the 'type' instead of 'ext' property on the dependencies in the client project (mistake of mine), I'll fix it on the develop branch.
Support Staff 2 Posted by Maxime Cowez on 13 Sep, 2012 12:54 PM
Hi Jim,
I just ran into the same issue while creating a new project and the reason I got this error was because I hadn't set up my multi-project correctly: I forgot to create the
settings.gradlefile in the root project. Which is why thegradlefxplugin didn't get applied to the subproject; hence thetypeproperty wasn't recognized. Perhaps that is what's happening to you too.@Yennick: can you think of any way we could catch this kind of error and display a proper error message?
Support Staff 3 Posted by Yennick Trevels on 13 Sep, 2012 01:15 PM
We can add a validator for the type property, but that doesn't catch the missing settings.gradle file. I guess that's something Gradle should catch.
In Jim's case it was the 'ext' property on the dependency that was named 'type' by accident. He used one of our sample projects, so a missing setttings.gradle file isn' the problem here.