[
https://issues.apache.org/jira/browse/FELIX-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188911#comment-15188911
]
Fabian Lange commented on FELIX-5210:
-------------------------------------
BTW: you also cannot force a patch release. So If my version selector says
{code}
<version>[1.0.5,2.0.0)</version>
{code}
or now
{code}
<version>1.0.5</version>
{code}
the plugin will generate
{code}
;version="[1.0,2)
{code}
even though I know i am not compatible with 1.0.4 - yes that is a stretch on
sem-ver but If there exists a bug, I know I cannot work with, this is actually
valid.
> 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)
