Skip to content

Reflective access with CGLIB breaks windowbuilder in java 16 and higher #45

Closed

Description

@wimjongman

Hi,
I receive an 'Unhandled event loop exception' exception (see attached) only when Eclipse runs JDK16.
When I use JDK16 for my workspace it works.

I use Eclipse 4.19 with JDK16 patches.

stack2.txt

Activity

  1. wimjongman commented on Jun 4, 2021

    @wimjongman
    ContributorAuthor

    It works well when I use " --illegal-access=permit" (in eclipse.ini) as proposed by Laurent.

  2. added this to the 1.9.8 milestone on Jun 4, 2021
  3. howlger commented on Jun 22, 2021

    @howlger
    Contributor

    Lombok fixed the problem (which I guess is the same) as follows:
    projectlombok/lombok@7069c7e

  4. added 3 commits that reference this issue on Oct 17, 2021
  5. lcaron commented on Oct 17, 2021

    @lcaron
    Contributor

    Bug fixed in WB 1.9.8

  6. wimjongman commented on Oct 18, 2021

    @wimjongman
    ContributorAuthor

    Laurent, if I understand correctly, this addition will allow cglib to keep running by calling the 'exportAllModulesToAllModules()' method? Is this done for the complete jvm?

    https://www.burningwave.org/

  7. lcaron commented on Oct 18, 2021

    @lcaron
    Contributor

    Yes wim, as far as I understand it is done for the complete JVM

  8. cniweb commented on Jun 27, 2022

    @cniweb

    It works well when I use " --illegal-access=permit" (in eclipse.ini) as proposed by Laurent.

    The argument --illegal-access=permit is no longer supported with Java 17.

  9. wimjongman commented on Jun 27, 2022

    @wimjongman
    ContributorAuthor

    I don't think we need that anymore since we switched technologies. @lcaron can you confirm?

  10. merks commented on Jun 27, 2022

    @merks
    Contributor

    A while back, I added this to make it work with Java 17, but I don't know if that's still needed either:

    --add-opens=java.base/java.lang=ALL-UNNAMED
    
  11. howlger commented on Jun 27, 2022

    @howlger
    Contributor

    I don't think we need that anymore since we switched technologies. @lcaron can you confirm?

    Yes, in recent versions --illegal-access=permit is not used/required anymore.

    See also #280 (not yet released)

  12. lcaron commented on Jun 27, 2022

    @lcaron
    Contributor

    The trick with --illegal-access=permit was necessary with Java 16, but it is no longer supported in Java 17.

    Anyway the latest release of WB runs without additionnal VM parameter on Java 16+

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions