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

Replace Deployment Processors Javax dependencies with Jakarta module identifiers


    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • 28.0.0.Final
    • None
    • None
    • None

      A natural choice to exclude a module from deployment would be to use the module name that contains the jar(s) I want to exclude.

      However, at this moment and as part of our process to transition to Jakarta EE 10, WildFly deployment processors are still adding the (javax) module alias instead of the target module (jakarta). For example, to exclude jakarta.activation-api-2.1.1.jar I have to exclude javax.activation.api alias instead of jakarta.activation.api

      That makes it more difficult to correctly identify which module I need to exclude on my deployment.


            yborgess1@redhat.com Yeray Borges Santana
            yborgess1@redhat.com Yeray Borges Santana
            0 Vote for this issue
            3 Start watching this issue