You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Fabian Lange (JIRA)" <ji...@apache.org> on 2016/03/10 08:56:40 UTC

[jira] [Commented] (FELIX-5210) maven-bundle-plugin picks too restrictive version

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

Fabian Lange commented on FELIX-5210:
-------------------------------------

I have not yet checked how the plugin works, but maven selects the 1.1.0 version of the dependency for the build cycle. if the plugin only takes the first two numbers from the maven selected version, that is the reason. Still not good

> 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)