[ https://issues.apache.org/jira/browse/FELIX-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189172#comment-15189172 ]
Stuart McCulloch commented on FELIX-5210: ----------------------------------------- BTW you can override the default semantic versioning policy used by bnd: If your bnd instructions are in a separate ".bnd" file use: {code} -consumer-policy: ${range;[===,+)} {code} Whereas if your bnd instructions are in the pom file use: {code} <_consumer-policy>$${range;[===,+)}</_consumer-policy> {code} http://bnd.bndtools.org/chapters/170-versioning.html has more details, including why the default doesn't include the micro version. > 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)