[jira] [Created] (JCR-4060) unintended export versions due to changed defaults in maven bundle plugin

["Julian Reschke (JIRA)" <ji...@apache.org>]

Julian Reschke created JCR-4060:
-----------------------------------

             Summary: unintended export versions due to changed defaults in maven bundle plugin
                 Key: JCR-4060
                 URL: https://issues.apache.org/jira/browse/JCR-4060
             Project: Jackrabbit Content Repository
          Issue Type: Bug
    Affects Versions: 2.13.4, 2.12.5
            Reporter: Julian Reschke


It appears that the maven bundle plugin change for JCR-3937 has caused default export version numbers to be assigned where before we hadn't any.

For instance, in jackrabbit-api, the package "o.a.j.api" has a package-info.java setting the version to 2.4, and this is what get's exported.

However, o.a.j.api.query does not have a package-info, and now gets exported with a version number of 2.13.5, whereas previously it didn't get any version number.

a) Does anybody know whether this change in behavior of the bundle plugin is documented anywhere?

b) Do we need to fix something here, or are automatically assigned version numbers indeed ok? If we need to do something, what is the correct fix? Freeze the version numbers at the currently assigned version?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)