Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6635

Make org.wildfly.core.launcher.* more extensible

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 23.0.0.Beta5, 23.0.0.Final
    • 20.0.2.Final
    • Launcher
    • None

    Description

      As part of the current Jakarta EE 11 TCK refactoring work we will need new launchers to replace the CTS command line runners for application client and embedded EJB tests. When I tried adding an application client Arquillian container to the https://github.com/wildfly/wildfly-arquillian repo, I found I could not use classes like 
      org.wildfly.core.launcher.AbstractCommandBuilder due to package private access on the class.
       
      Is there is a requirement that all launchers exist in the wildfly-launcher module?

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFARQ-140 Add EE appclient support to the the container-managed module

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              jperkins-rhn James Perkins
              rhn-engineering-sstark Scott Stark
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: