[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604050#action_12604050
]
Rajini Sivaram commented on TUSCANY-2343:
-----------------------------------------
Daniel,
Do you have a date that you would require a bundle-ized Tuscany to be ready by
to match with your release dates? It is definitely not going to be ready in
time for the 1.3 release - do you require a released version?
Sebastian,
The DynamicImport-Package statements in the 3rd party jars are temporary (they
were used to generate virtual bundles on the fly), and will be replaced with
explicit versioned import statements, probably generated using
maven-bundle-plugin. There may be a few dynamic imports left in Tuscany, but
they will be specific ones that are not wildcarded.
- Rajini
> OSGi bundle design leads to class loading issues
> ------------------------------------------------
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
> Reporter: Georg Schmidt
> Attachments: Libary Versions.xls, test_bundles.zip
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
