I have a Gradle root project with two subprojects, one called "app", the other "lib". Now I'm trying to import the lib project into the app project and put this in the app project's build.gradle:

dependencies {
    implementation project(':my-lib')
}

"gradle build" runs flawlessly from the command line, but the IDE throws up.

Whenever I initially add the above dependency to the build.gradle file or subsequently select "Reload Project", there appears a popup in the lower right corner of the IDE that says "app has some issues".

When I click on this issue I get a message of category WARNING with priority LOW. It says:

Could not resolve all files for configuration :app:compileClasspath".
Could not resolve project :my-lib.

Now, even though this is just a low priority warning, it completely kills the IDE, because none of the imported dependencies can be resolved anymore. Not only the my-lib dependency, but all others (Spring, Apache Commons etc.) as well. All my imports in all Java source files turn red and none of the IDE functions (refactoring, fix imports etc.) work anymore.

As soon as I remove the my-lib dependency, everything goes back to normal in the IDE. Again, Gradle has no problems resolving the my-lib dependency from the command-line, it is just the IDE that cannot deal with it. Restarting the IDE did not help.

So I assume some files in Netbeans became corrupt - is there any cache or other files I can delete?

Many thanks in advance for any pointers,

Ulrich


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to