-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IntelliJ IDEA import fails because it is not honoring gradle.properties #30
Comments
Is it a Gradle or IntelliJ issue? |
If IntelliJ uses |
So I added |
We've gotten similar reports on the forum about certain JVM args not being honoured. We should investigate whether this is a bug in the tooling API. Can you open a bug on the gradle/gradle issue tracker? |
Thanks, @oehme looking into it. I will create an issue. |
Better late then later :( gradle/gradle#6825 |
We are enabling experimental features via system properties which are set in
gradle.properties
Those properties are read in different places. One of them is in init script. However, when IntelliJ is importing gradle project it is setting properties fromgradle.properties
too late and init script is already executed. Example project showing this case https://github.com/nebula-plugins/gradle-nebula-integration/tree/master/broken-intellij-import-with-native-lockHow to reproduce
cp init.gradle ~/.gradle/init.d/
./gradlew dependencies --write-locks
idea .
(assuming that you have IntelliJ command line launcher)OK
to finish import.Project import fails with:
Looking at IntelliJ IDEA import process logging shows that flag for coreBomSupport is false hence it didn't exclude
resolutionRules
from recommending and so recommender adds bom into it. Because lock was generated from command line where it was excluded it causes missmatch.The text was updated successfully, but these errors were encountered: