[
https://issues.apache.org/jira/browse/FELIX-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188898#comment-15188898
]
Fabian Lange commented on FELIX-5210:
-------------------------------------
Hi Christian. you are right. This is a bit counter intuitive, but maybe there
is no better way.
The maven-bundle-plugin will automatically generate a version range into the
manifest according to sem-ver. But if I use the same intended range as maven
range, the resolver picks the newest version, which then in turn feeds into the
maven-bundle-plugin.
Not sure what to do. close issue, document (better?), workaround in plugin?
> maven-bundle-plugin picks too restrictive version
> -------------------------------------------------
>
> Key: FELIX-5210
> URL: https://issues.apache.org/jira/browse/FELIX-5210
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Fabian Lange
>
> I am using the maven bundle plugin to build my manifests.
> What I just noticed is that it is too restrictive on versions.
> I have a dependency saying
> {code}
> <version>[1.0.0,2.0.0)</version>
> {code}
> But the bundle plugin (2.5.4 and 3.0.1) generate
> {code}
> ;version="[1.1,2)
> {code}
> while the 1.1 version does exist, my bundle would happily work with 1.0,
> which is also what my maven config says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
