This usually goes away for me if I reload the project after building to ensure the classes being imported have been compiled. It would certainly be better if that wasn’t required.
Scott > On Jun 21, 2021, at 8:35 AM, Christian Pervoelz <cpervo...@gmail.com> wrote: > > > Hi, > > I have a gradle container project consisting of two sub projects. > Clean, Build, Run, Debug, etc.works properly as it should from NetBeans. > > But... every single import statement is marked as "package does not exist". > This applies to > imports from external libraries > imports from the other project > imports from the same project, but a different package > > This causes a lot of follow-up problems (e.g. not working code completion, > tons of markers in the side bar about issues), which are quite inconvenient > to work with. It feels like working with a simple text editor, that has a bit > of code coloring and formatting capabilities. > There is also another nasty side effect: When creating a new class in a > project, the file is created, but misses the package declaration. (But even > after adding it manually, the class is still unknown to other classes) > > > So, my question is: > Might it be, that a gradle project in NB, that is depending on other gradle > projects is not able to use the classpaths given in the project settings > (which are all shown)? Or is it just ignoring those? > > Further information: > Windows 10, Gradle 7, OpenJdk 16 > > --- Thanks in advance > C.
