Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-464

[Bootable JAR plugin/JDK17] Missing modular export when enabling dns.ping protocol

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Compatibility/Configuration, User Experience
    • Workaround Exists
    • Hide

      The issue can be workarounded by setting: JAVA_OPTS_APPEND=--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED

      Show
      The issue can be workarounded by setting: JAVA_OPTS_APPEND=--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED

      This issue affects the latest productized Bootable JAR plugin, i.e. 6.1.2.Final.

      An modular JDK export - i.e. jdk.naming.dns/com.sun.jndi.dns is not added to the JAR manifest when building a Bootable JAR which is configured with the <cloud/> option.

      Such export is needed in order to let the custer member discovery mechanism work properly with modular JDK based images (e.g.: the OpenJDK17 image).

      Upstream issue: https://github.com/wildfly-extras/wildfly-jar-maven-plugin/issues/301

      The agreed resolution is to have another micro version of the 6.x plugin released and productized for EAP XP4 Bootable JARs, while WIldFly Bootable JARs can be built with the 7.x version of the plugin that contains the fix already.

            jdenise@redhat.com Jean Francois Denise
            fburzigo Fabio Burzigotti
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: