New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REGRESSION] Gradle "Project Problems" #7365
Comments
Just did a start/close of NB and am attaching the log. The first indication of trouble is
|
Just tried with RC3, sames problems |
That is a class build for JDK 17. My gut feeling the asm Version that complains there is to old. |
I'm not sure what you're saying. What is "That", the first word of the comment, referring to? This works with NB-21 running under JDK-21. |
That class that is being processed by asm according to the stack trace. But this:
Makes no sense. NB bundles asm 9.7 and gradle 7.4 bundles asm 9.2. Both should support JDK 17 (9.2 is documented to support JDK 18 classes). My gut feeling: Someone decided it would be a good idea that the gradle tooling API passed java bytecode from the caller (NetBeans IDE) to the project being worked on. If that is the case, the asm version relevant here is the one in the gradle being targetted. If that asm version supported JDK 11, it would have worked because the bytecode level for the @lkishalmi what do you think? |
I didn't even think about the class file version. The project is compiled for
|
My guess is that the Java version upgrade from 8 to 17 in #7257 needs reverting prior to release. This line seems to pass Looking at the docs of |
will try to investigate / fix tomorrow |
Yes, that's the issue. Revert could work. For the next release it would be better to split the |
i am usually for reverts in situations like this. But if the lang level of the module is what causes this, this can be trivially fixed until a better solution is found. -> #7367 (untested) bonus: fixes two evil |
@mbien 👍 - totally agree - I meant reverting the language level change, not the whole lot. Had also taken a quick look at what was involved, but hadn't got around to looking at the changes. PR looks good to me at a glance. I hadn't realised that the Gradle Tooling API offered this weird hacky thing with serialization and bytecode loading in the daemon from the IDE classes. |
@mbien It comes up cleanly without "Project Problems". I've tried a few things, it's looking good. |
Apache NetBeans version
Apache NetBeans 22 release candidate
NOTE: both RC2 and RC3
What happened
Download RC-2, copy NB-21 userdir, Start NB, Gradle Project Problems.
Language / Project Type / NetBeans Component
Gradle
How to reproduce
Using project and sole sub-project from
https://github.com/errael/astrology-castro
BRANCH: LogOps
See png attachment
But ends with Cannot Load, See png attachement (NOTE the gradle-6.8.3)
NOTE After clean build there are many bogus warnings about "unused"
Did this work correctly in an earlier version?
Apache NetBeans 21
Operating System
Linux harmony 6.8.0-76060800daily20240311-generic #202403110203
171320690822.04~3a62479 SMP PREEMPT_DYNAMIC Mon A x86_64 x86_64 x86_64 GNU/LinuxJDK
JDK-21/JDK-11
Apache NetBeans packaging
Apache NetBeans binary zip
Anything else
No response
Are you willing to submit a pull request?
No
The text was updated successfully, but these errors were encountered: