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

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.12.5, 2.13.4
• Fix Version/s: 2.13.6, 2.14, 2.12.7
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 24/Nov/16 14:13
• Updated: 17/Dec/16 08:12
• Resolved: 13/Dec/16 14:16

Description

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?

Issue Links

• is broken by: JCR-3937 jackrabbit-jcr-commons bundles incorrectly has google dependency in Export-Package uses clause
• relates to: FELIX-5172 Better control over default export version
• relates to: JCR-1342 Create OSGi Bundle Manifest Headers
• relates to: JCR-4084 decide on frozen export version numbers