[
https://issues.apache.org/jira/browse/OAK-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885150#comment-13885150
]
Felix Meschberger commented on OAK-1362:
----------------------------------------
+1 to using package-info.java. The additional benefit actually is that you can
put package level JavaDoc into this file instead of having to maintain
package.html file in the resources.
As for versions: Starting with 1.0 for new packages is bets. For existing
packages which have so far been exported with the library/bundle version, we
should start from the last version. And yes, using the library/bundle version
for the exported version is wrong since it increases the version on each
release, regardless of any changes.
As for checking: I agree with [~jukkaz] that tooling support would be helpful:
The BND library has some version support built in, but this is not exposed in
any Maven plugin yet. But the Aries project has a version check plugin which
can be leveraged and which breaks the build if semantic versioning is not
obeyed.
> 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
>
> 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)
