On 2020-01-02, Oliver Heger wrote: > The change of the bundle name does not necessarily break all OSGi users. > AFAIK, the recommended way to use an OSGi bundle is to import the > packages, not to require a specific bundle - this use case would not be > affected by the change of the bundle name.
Ah, I see. This is backed by Julian Reschke's comment https://issues.apache.org/jira/browse/COMPRESS-498?focusedCommentId=17006749&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17006749 where he says ,---- | same code in two different artefacts `---- would be the problem. So I guess we are confusing the OSGi container if Compress 1.17 and 1.18 are available as artifacts. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
