> The first thing I would recommend you do is a clean check out of the project
> (assuming it's in a git repo or something) into a new directory.
I have done that. And deleted the NetBeans cache as well. But the problem comes
back as soon as I open a sub-project that references (already compiled
The first thing I would recommend you do is a clean check out of the
project (assuming it's in a git repo or something) into a new directory.
If the issue persists, then do the same thing on a fresh container,
which could be derived from an image like gradle:7-jdk17. That way you
will have a cl
Greetings,
Well, yes, I've had gradle issues in the past due to work projects. It is
rather important that
the people trying to fix issue X have a way to ensure that they are using code
that invokes
issue X to see if they are actually fixing issue X.
_*Nobody*_ expects you to publish your n
Well, I can't show the real project (customer project with NDA). And I can't
just create a project of that size (35 projects, 550K lines of code).
And besides I don't have a Github account.
The problem is, that basically every problem I have with NetBeans and Gradle
only happens on bigger projec
Create a simple example in GitHub or GitLab so that people have something to
test against.I'm not sure how your project is set up, since I normally don't
use the term "module" in gradle projects.Sent from my Galaxy
Original message From: Thomas Kellerer Date:
6/26/23 01:17 (G
