[jira] [Created] (AXIS2-6105) Remove OSGi bundle packaging from transport modules

Robert Lazarski created AXIS2-6105:
--------------------------------------

             Summary: Remove OSGi bundle packaging from transport modules
                 Key: AXIS2-6105
                 URL: https://issues.apache.org/jira/browse/AXIS2-6105
             Project: Axis2
          Issue Type: Task
            Reporter: Robert Lazarski


The transport modules (local, base, tcp, udp, jms, mail, xmpp) still use <packaging>bundle</packaging> with the maven-bundle-plugin.
  This is the last remaining OSGi dependency in Axis2 after AXIS2-6105 removed the OSGi modules and Eclipse/IntelliJ plugins.

  OSGi missed the Jakarta EE 9+ transition and the maven-bundle-plugin is no longer actively maintained. The bundle packaging should be
   replaced with standard <packaging>jar</packaging>.

  The Automatic-Module-Name manifest entries added in AXIS2-6040 already provide stable module identity for Java 9+ JPMS, which is the
  modern replacement for OSGi's Bundle-SymbolicName. The remaining bundle plugin features (Export-Package, Bundle-Name, Bundle-Vendor)
  have no equivalent consumer in a post-OSGi world.

  Scope:
  - Convert 7 transport modules from <packaging>bundle</packaging> to <packaging>jar</packaging>
  - Remove maven-bundle-plugin configuration from each
  - Verify Automatic-Module-Name is served via maven-jar-plugin (already in place for transport-local from AXIS2-6040)
  - Add Automatic-Module-Name for the 6 transport modules not covered by AXIS2-6040 (base, tcp, udp, jms, mail, xmpp)

  Affected modules:
  {code}
  modules/transport/local  — already has Automatic-Module-Name (AXIS2-6040)
  modules/transport/base
  modules/transport/tcp
  modules/transport/udp
  modules/transport/jms
  modules/transport/mail
  modules/transport/xmpp
  {code}





--
This message was sent by Atlassian Jira
(v8.20.10#820010)