[
https://issues.apache.org/jira/browse/OAK-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886470#comment-13886470
]
Felix Meschberger commented on OAK-1362:
----------------------------------------
bq. why not start with a clean scheme and set them to 1.0, too?
It may not be an issue for Oak, but for example in Jackrabbit consider the
Jackrabbit API bundle: A consumer might be built against v 2.3.0 and thus may
import (2.3.0,3]. Now you think that you want to fix this
package-version-equals-bundle-version problem and set the export version to
1.0. This causes the consumer bundle to not resolve any longer because the
export version 1.0 is outside the range (2.3.0,3] required by the consumer
bundle.
> Add package-info.java files instead of using the project version for the
> package exports
> ----------------------------------------------------------------------------------------
>
> Key: OAK-1362
> URL: https://issues.apache.org/jira/browse/OAK-1362
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
> Fix For: 0.16
>
>
> the current code lacks of package-info.java with BND information for the
> exported java packages. the default bundle plugin builds therefor bundles
> with package exports that use the project version, which is not best practice.
> we should add package-info.java with bnd information for all exported
> packages.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
