[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468907#comment-17468907
]
Thomas Schapitz edited comment on NETBEANS-6349 at 1/4/22, 10:58 PM:
---------------------------------------------------------------------
I didn't check for 12.5 explicitly, I simply concluded that from the linked
NETBEANS-6064, which was stated to have occurred on 12.5. That said, and as
I've mentioned on the DEV list, I'm currently trying to be of some help, by
working my path through the open issues. In the process, I found the 7 linked
Issues, that are all connected by the cause explained here.
>From a personal as well a resources point of view I simply would wait that out
>until 13.0 becomes available, which would remedy problem as described in the
>workaround section.
But it might indeed be sensible to spawn a discussion on dev, on whether and
how to proof our builds with respect to cross JDK compilation. The problem we
look at here is, that this sort of build compromises the compilers guarantees
for static link checking, namely, that the statically compiled code will
execute without causing NoSuchMethodErrors, or similar. Problems like this are
always likely to slip through, when using an earlier JDK during execution, then
where used during compile and test. This might happen too when using a later
JDK, but is much less likely then.
Personally, I'm not affected by this, because I usually try to switch as early
as possible, especially within the IDE. Having been prompted by these issues to
look into the prerequisites, I was indeed surprised, that JDK 8 is still deemed
sufficient there, else I would have closed those Issues as 'invalid' outright.
So yet another way to fix this, would be to retrofit the release notes for NB
12.5+. This again, would be something for the dev list to discuss.
At the very least, this issue may now serve as an temporary anchor for all
similar ones, that might still hide in the issues not yet reviewed.
was (Author: taps):
I didn't check for 12.5 explicitly, I simply concluded that from the linked
NETBEANS-6064, which was stated to have occurred on 12.5. That said, and as
I've mentioned on the DEV list, I'm currently trying to be of some help, by
working my path through the open issues. In the process, I found the 7 linked
Issues, that are all connected by the cause explained here.
>From a personal as well a resources point of view I simply would wait that out
>until 13.0 becomes available, which would remedy problem as described in the
>workaround section.
But it might indeed be sensible to spawn a discussion on dev, on whether an how
to proof our builds with respect to cross JDK compilation. The problem we look
at here is, that this sort of build throwing out the compilers guarantees for
static link checking, namely, that the statically compiled code will execute
without causing NoSuchMethodErrors, or similar. Problems like this are always
likely to slip through, when using an earlier JDK during execution, then where
used during compile and test.
Personally, I'm not affected by this, because I usually try to switch as early
as possible, especially within the IDE. Having been prompted by these issues to
look into the prerequisites, I was indeed surprised, that JDK 8 is still deemed
sufficient there, else I would have closed those Issues as 'invalid' outright.
So yet another way to fix this, would be to retrofit the release notes for NB
12.5+. This again, would be something for the dev list to discuss.
At the very least, this issue may now serve as an temporary anchor for all
similar ones, that might still hide in the issues not yet reviewed.
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> ---------------------------------------------------------------------------------
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing & Indexing
> Affects Versions: 12.5, 12.6
> Reporter: Thomas Schapitz
> Priority: Critical
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
