[
https://issues.apache.org/jira/browse/DBCP-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179795#comment-15179795
]
Philipp Marx commented on DBCP-454:
-----------------------------------
With the fix the bundle doesn't contain the duplicate import packages anymore.
Still the bundle can't be resolved properly in my OGSi environment (karaf 3.0.5
/ java 1.8 / MacOS). If I remove the extra import declarations for
"javax.transaction" completely it works without problems. Are we sure that
these declarations are absolutely required in the bundle? Isn't it the
responsibility of the runtime to ensure the packages are properly exported,
i.e. Karaf seems to take care of this?
> OSGi declarations contain multiple import headers for javax.transaction
> -----------------------------------------------------------------------
>
> Key: DBCP-454
> URL: https://issues.apache.org/jira/browse/DBCP-454
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: OSGi
> Reporter: Philipp Marx
> Priority: Trivial
> Attachments: patch
>
>
> In DBCP-445 an issue for "javax.transaction" import-packages was addressed.
> Though with the fix for this issue the import-packages will contain
> "javax.transaction" twice:
> Import-Package: javax.management,javax.naming,javax.naming.spi,javax.s
> ql,javax.transaction,javax.transaction.xa,org.apache.commons.logging,
> org.apache.commons.pool2,org.apache.commons.pool2.impl,javax.transact
> ion.xa;version="1.1.0";partial=true;mandatory:=partial,javax.transact
> ion;version="1.1.0"
> Thus the bundle can't be loaded as duplicate import declarations are
> prohibited and i.e. Felix will complain about this and refuse to install the
> bundle. The fix is quite simple by appending the '*' to the end (see attached
> patch).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
