[
https://issues.apache.org/jira/browse/COMPRESS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517338#comment-16517338
]
Jérémie Brébec commented on COMPRESS-456:
-----------------------------------------
I agree with Oliver, it's better to explicitly declares dependencies and
optional dependencies.
However, it's look like the guys behind commons-compress doesn't use osgi or
are not used to it ;) Then every times a new dependency is added, if the
Import-Package directive is not modified, this dependency will be mandatory and
the bundle will not deploy on osgi. This will probably end with new Jira issue
for each new dependency..
That's why for this kind of project, I personnaly prefer to explicitly declare
mandatory dependencies, and let everything else be optional.
> Missing OSGI Import-Package
> ---------------------------
>
> Key: COMPRESS-456
> URL: https://issues.apache.org/jira/browse/COMPRESS-456
> Project: Commons Compress
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.17
> Reporter: Jérémie Brébec
> Priority: Major
> Fix For: 1.18
>
>
> The configuration of the maven-bundle-plugin overrides the <Import-Package>
> directive : "*" is not present anymore, and severals packages do not resolve
> correctly.
> For example, "javax.crypto", which is used by 7z encryption, is not resolved
> and using this feature fails with a ClassNotFoundException on
> javax.crypto.SecretKey.
> ahma I think that the correct Import-Package directive should be :
> {code:java}
> <Import-Package>*;resolution:=optional</Import-Package>{code}
> this directive will import everything commons-compress depends on, but with
> an optional resolution (and so every dependencies will be optionals)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
