Within a few days (maybe today) there will be a patch release to fix
some severe Gradle issues. Suggest trying that and see how things go.
distributed directly on our NetBeans 16 Update Center.
There are no other binaries planned for this release.
Apache NetBeans 16-u1 contains only two module updates:
- org.netbeans.modules.gradle
- org.netbeans.modules.gradle.java
The list of PR-s in this release above NetBeans 16:
https://github.com/apache/netbeans/milestone/21?closed=1
-ernie
On 23/01/03 9:30 AM, Ulrich Mayring wrote:
I forgot to mention that deleting the Netbeans Cache did not help.
What does work sometimes (but not all of the time!) is when I create a
new subproject in a different subdirectory. However, when I rename
that to the name of the problematic subproject, then things break again.
So it seems that some names of problematic subprojects are somehow
cached somewhere and probably in a corrupted way. What do I need to
delete here to get back the ability to use any name I want for my
subproject?
These are not especially weird names, for example app-api or app-api2
work, but app-ui or app-gui don't. There must be some corrupted files.
Kind regards,
Ulrich
Am 03.01.23 um 13:31 schrieb Ulrich Mayring:
Hi all,
I have a Gradle 7.5 based multi-project build on Netbeans 16 with
Java 17. One of my subprojects cannot be loaded, the IDE displays
"Priming Build required", but when I click on "resolve", then nothing
much happens (there is some messages "preparing priming build" for a
short time).
The whole project including the one subproject builds flawlessly from
the command line and from within the IDE. But I cannot open the
problematic subproject, the IDE does not initialise it at all and,
for example, does not recognize the imports, so all my code is red.
I have tried to start the IDE with Java 11 and I have tried to set
Tools/Options/Java/Gradle to 7.5, but to avail.
The problematic subproject is actually visible in the IDE, but the
build.gradle could not be parsed, which I can see from the name of
the project, which is set to "foo" in the build.gradle like this:
description = 'foo'
This should display the project as "foo" in the IDE, if the
build.gradle could be parsed. But it displays as the name of the
filesystem folder it is located in, so it's pretty clear that the
build.gradle could not be parsed and thus all my dependencies could
not be loaded.
I've had this before a couple of times, but whenever I could "clean
build" the project, the problem usually went away - sometimes an IDE
restart was required.
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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