[
https://issues.apache.org/jira/browse/KARAF-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127824#comment-15127824
]
Markus Rathgeb commented on KARAF-4105:
---------------------------------------
I am a little bit irritated about the version handling here.
There is a TODO, that version ranges are currently ignored at all
(https://github.com/apache/karaf/blob/karaf-4.0.4/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L1089).
The PR I created should solve some problems, but I assume that the feature
resolver handles version correctly already.
Somewhere in the Karaf code versions and version ranges are handled correctly
(I think so).
Why can't we reuse that version handling instead of implement a new one?
Could you (e.g. [~jbonofre]) point me to that code and how to reuse it
correctly (as we extend the profile feature we should not create a bunch of
dependencies, I assume.)
> karaf-assembly fails when used Maven versions do not match derived OSGi
> versions
> --------------------------------------------------------------------------------
>
> Key: KARAF-4105
> URL: https://issues.apache.org/jira/browse/KARAF-4105
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 4.0.3
> Reporter: Oliver Lietz
> Assignee: Jean-Baptiste Onofré
>
> e.g. {{$\{project.version\}}} {{0.1.1-SNAPSHOT}} and {{0.1.1.SNAPSHOT}} do
> not match in {{org.apache.karaf.profile.assembly.Builder}}
> See mail thread [\[K4.0.3\] custom distribution and
> kar|http://mail-archives.apache.org/mod_mbox/karaf-user/201511.mbox/%3c7781910.EKNrsAyV2X@madness%3e]
> for more.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
