Build Script Parsing - kelemen/netbeans-gradle-project GitHub Wiki

In case you are using Gradle 1.9 or above, the plugin now can do a better analysis of your build script. This new build script evaluation strategy is enabled by selecting the "Newest possible" strategy. However, this strategy no longer relies on the "idea" plugin of Gradle. If the old evaluation strategy worked for you but this new strategy does not, you can switch back to the old method by selecting "Idea plugin based".

Important note: When you are using the new strategy, the sources are no longer downloaded automatically. Instead, you have to manually request so in the context menu of the "Dependencies" node.

Allows using the new API introduced in Gradle 1.8 (note that Gradle 1.8 is itself broken, no matter what API is being used). You should have this checkbox checked unless it breaks something for you as it understands your project better. Note that when using the new API, sources are not downloaded automatically but can be downloaded by right clicking the dependencies node in the project view.

If checked, the plugin will first load the root Gradle project first and determines if the project to be loaded is part of the multi-project build of the (assumed) root project. This preloading is only needed when there is a project inside a multi-project build without its own settings.gradle. If the root project was not checked first, then loading this internal, separate project would fail (because Gradle would assume that it is part of the root multi-project build).

Loading the root project first should have no noticeable side effect. However, if for some reason this feature causes some unforseen issue for you, you can disable it (otherwise, it is safe to keep enabled).

You may allow the plugin to try to deduce the required Java version from the build scripts. That is, from the sourceCompatibility and the targetCompatibility properties. Note however, that for this to work properly, you have to apply the idea plugin (yes, not a typo, you need the idea plugin) on the root project. Also, you have to also apply the java plugin before applying the idea plugin on the root project. If you don't want to apply the java plugin, then you have to manually adjust the idea.project.jdkName and the idea.project.languageLevel properties in the root project.

This option is ignored when using the new API introduced in Gradle 1.8 as the new API is reliable without extra configuration.