[jira] [Commented] (FELIX-5533) Fix a semantic versioning issue when releasing dependency manager

["Bram Pouwelse (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859633#comment-15859633 ] 

Bram Pouwelse commented on FELIX-5533:
--------------------------------------

Hi Pierre, 

I think 2 is not a solution but it's a way to mask the problem in Eclipse but it can sill be useful to add the {{-fixupmessages}}. Changing the baselining error to a warning in Eclipse has two advantages: 
 - If a project on which other projects in the workspace depend has a baselining error these projects can still be built so you get a lot less red crosses and errors.
 - Because the build completes you can use the "Release Workspace Bundles..." dialog (available from the Bndtools menu) to analyze the baselining issue (in that view the released bundle is compared to the current workspace version).

You can forget to fix the warning in Eclipse but the baselining error will still fail the Gradle build so you should notice that soon enough.  

> 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 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:
> {code}
> # 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}
> {code}
> 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
(v6.3.15#6346)