felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FELIX-5533) Fix a semantic versioning issue when releasing dependency manager
Date Thu, 09 Feb 2017 14:53:41 GMT
Pierre De Rop created FELIX-5533:

             Summary: Fix a semantic versioning issue when releasing dependency manager
                 Key: FELIX-5533
                 URL: https://issues.apache.org/jira/browse/FELIX-5533
             Project: Felix
          Issue Type: Task
          Components: Dependency Manager, Dependency Manager Annotations, Dependency Manager
Lambda, Dependency Manager Runtime, Dependency Manager Samples, Dependency Manager Shell
    Affects Versions: org.apache.felix.dependencymanager-r1
            Reporter: Pierre De Rop
            Assignee: Pierre De Rop
             Fix For: org.apache.felix.dependencymanager-r9

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

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

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.

This message was sent by Atlassian JIRA

View raw message