[
https://issues.apache.org/jira/browse/FELIX-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860260#comment-15860260
]
Pierre De Rop commented on FELIX-5533:
--------------------------------------
Thanks Bram, I do agree and I have added the fixupmessages message in the
configuration.
Now, unlike what I said in our private discussion this afternoon, it turns out
that including the sources and using the fixupmessages only resolves the
baselining issue in eclipse, but not using gradle only. But may be I finally
have found the real root cause of all my problems: in the root
gradle.properties file, I was having this:
bnd_plugin=biz.aQute.bnd:biz.aQute.bnd.gradle:3.1.0
I fixed the above by:
bnd_plugin=biz.aQute.bnd:biz.aQute.bnd.gradle:3.3.0
and ... it seems to be now fully working (either using eclipse or gradle only)
!
I think I can now go for a release -:)
> 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)
