You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2014/01/28 20:54:38 UTC
[jira] [Comment Edited] (OAK-1362) Add package-info.java files
instead of using the project version for the package exports
[ https://issues.apache.org/jira/browse/OAK-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884518#comment-13884518 ]
Tobias Bocanegra edited comment on OAK-1362 at 1/28/14 7:53 PM:
----------------------------------------------------------------
bq. On a related note, can we set up some tooling to check and/or update the package versions semi-automatically?
why would you want that? that is exactly the idea behind the semantic versioning. the developer that changes the API of a class of an exported package, updates the package version. if nothing changes, the version remains the same.
was (Author: tripod):
bq. On a related note, can we set up some tooling to check and/or update the package versions semi-automatically?
why would you want that? that is exactly the idea behind the semantic versioning. the developer that changes the API of a class of an exported package, updates the package version.
> 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)