Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15438

End transformation of dom4j during build and use of the wildfly-preview feature pack


    • Initial Transformations

      During the build of the 'wildfly-preview' feature pack or the use of it in provisioning, the Galleon WildFly plugin is transforming the org.dom4j:dom4j library. The task here is to prevent this from occurring.

      The typical way to resolve this kind of thing would be to integrate a native jakarta namespace version of the artifact into the build, and that is a valid fix here too, but hopefully it won't be necessary (since I suspect dom4j will not produce such an artifact any time soon.)

      Instead, hopefully we can:

      1) Confirm that the artifact is being transformed solely due to its use of JAXB in its org.dom4j.jaxb package.

      2) Confirm that our uses of dom4j (by Hibernate or EclipseLink) do not involve use of that package, and therefore our supported use of dom4j doesn't require that package. (A scan by my IDEA installation indicates they don't, but I wasn't particularly careful about that check.)

      3) Remove the org.dom4j module's dependency on the javax.xml.bind.api module (since we don't support its use of that API.)

      4) Configure the build of the wildfly-preview FP to not transform org.dom4j:dom4j by adding a comment and an exclude element to the wildfly-galleon-maven-plugin config (see https://github.com/wildfly/wildfly/blob/main/ee-9/feature-pack/pom.xml#L387).

            smarlow1@redhat.com Scott Marlow
            bstansbe@redhat.com Brian Stansberry
            0 Vote for this issue
            3 Start watching this issue