[
https://issues.apache.org/jira/browse/AXIS2-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878369#action_12878369
]
Andreas Veithen commented on AXIS2-4311:
----------------------------------------
This means that we now have 3 different packagings for OSGi:
* All individual Maven modules produce OSGi bundles.
* modules/osgi produces an uber-bundle containing a subset of the Maven modules.
* modules/all produces another uber-bundle.
In addition to that, the root POM also produces an uber-JAR.
I don't know what others think about this, but I believe that this is
definitely too much. This creates confusion and is impossible to maintain
properly.
> Axis2 OSGi bundles have split packages
> --------------------------------------
>
> Key: AXIS2-4311
> URL: https://issues.apache.org/jira/browse/AXIS2-4311
> Project: Axis2
> Issue Type: Bug
> Components: adb, kernel, transports
> Affects Versions: 1.5
> Reporter: Raymond Feng
> Attachments: patch.txt
>
>
> 1) axis2-adb and axis2-kernel export "org.apache.axis2.util"
> 2) axis2-kernel and axis2-transport-http export "
> org.apache.axis2.transport.http"
> 3) axis2-kernel and axis2-transport-jms export
> "org.apache.axis2.transport.jms"
>
> These bundles are causing conflicts under OSGi as Import-Package is resolved
> in random order if they are split in multiple bundles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
