[FELIX-5533] Fix a semantic versioning issue when releasing dependency manager

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: org.apache.felix.dependencymanager-r1
• Fix Version/s: org.apache.felix.dependencymanager-r9
• Component/s: Dependency Manager, Dependency Manager Annotations, Dependency Manager Lambda, Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager Shell
• Assignee: Pierre De Rop
• Reporter: Pierre De Rop
• Created: 09/Feb/17 14:53
• Updated: 09/Feb/17 21:47
• Resolved: 09/Feb/17 15:01

Description

When you release the dm binary bundles using "gradle release" or when clicking on" BndTools -> Release Workspace Bundles ..."; then there is an issue with the bndtools semantic versioning: once you do "gradle release", then after once you clean and rebuild everything, the semantic versioning then complains and says that you have to increment the micro version of all released bundles.

With the help of the Luminis team, it turns out that there are two work arounds that can be done:

1) include the sources in released bundles, before doing "gradle release"

2) or declare the following in the bnd main configuration:

# Make baselining issues a warning instead of error when using Eclipse
fixuptype: ${if;${is;${gestalt;batch};batch};error;warning}

-fixupmessages: \
  "Baseline ...";is:=${fixuptype},\
  "The bundle version ...";is:=${fixuptype},\
  "The baseline version ...";is:=${fixuptype}

The two solutions are working.

For the moment, since including the sources in the bundles is helpful when debugging under eclipse and bndtools, I'm using the 1st solution: include the sources in binary bundles, using "-sources: true" in the main bnd config.