Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-31667

(7.3.z) wildfly-maven-plugin compatibility issue with Maven 3.9.0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 7.3.15.GA
    • Test Suite
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Steps to reproduce

      1. git clone git@github.com:jbossas/jboss-eap7.git -b 7.3.x
      2. Use Maven 3.9.0
      3. mvn clean install -DskipTests -Delytron

      Actual Result

      • No wildfly-maven-plugin is executed and appear in logs
      • CLI script enable-elytron.cli is not executed
      Show
      Steps to reproduce git clone git@github.com:jbossas/jboss-eap7.git -b 7.3.x Use Maven 3.9.0 mvn clean install -DskipTests -Delytron Actual Result No wildfly-maven-plugin is executed and appear in logs CLI script enable-elytron.cli is not executed

      The wildfly-maven-plugin configuration for the elytron profile fails to execute necessary CLI scripts in child modules like this when using Maven 3.9.0 and above. This is due to a change in how Maven handles profile inheritance, causing the profile to be unavailable to sub-projects.

      We must investigate and implement the necessary changes to the POM structure to ensure the elytron profile is correctly inherited and activated in sub-modules when using Maven 3.9.0+. This fix needs to be applied to both the jboss-eap7 and wildfly-core-eap repositories.

              gsamios Giorgos Samios
              gsamios Giorgos Samios
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: