Re: Can you make the maven bundle plugin use maven version ranges?

I agree that Martin has probably done the right thing... even having tested the various versions, which is above and beyond what most developers would bother to do. My criticism is aimed at the Wicket developers who have misused versions and forced Martin to do all this extra work! Regards, Neil

Re: Can you make the maven bundle plugin use maven version ranges?

I concede the point! :) - Ray On Thu, Mar 8, 2018 at 12:49 PM, Neil Bartlett wrote: > You don't actually have to duplicate anything. The lower bound appears in > two places but that can be handled with a property: > > > 6.0.0 > > > ... > > > ... >

Re: Can you make the maven bundle plugin use maven version ranges?

You don't actually have to duplicate anything. The lower bound appears in two places but that can be handled with a property: 6.0.0 ... ... ${wicket.base.version} ... org.apache.wicket.*; version="[${wicket.base.version}, 9)" On Thu, Mar 8, 2018 at 4:43 PM, Raymond Auge

Re: Can you make the maven bundle plugin use maven version ranges?

On Thu, Mar 8, 2018 at 11:37 AM, Neil Bartlett wrote: > If you're going to do this I would recommend instead building against the > floor version 6.0.0 (i.e. 6.0.0 in the dependency > section of the pom) and overriding the Import-Package with a simpler rule > as follows: >

Re: Can you make the maven bundle plugin use maven version ranges?

On Thu, Mar 8, 2018 at 11:24 AM, Raymond Auge wrote: > Totally +1 what Neil said. > > However there is one work around you can take if you really want to open > yourself up like that... > > http://bnd.bndtools.org/macros/range.html > > Specifically applied like so: > >

Re: Can you make the maven bundle plugin use maven version ranges?

Totally +1 what Neil said. However there is one work around you can take if you really want to open yourself up like that... http://bnd.bndtools.org/macros/range.html Specifically applied like so: Import-Package: org.apache.wicket.*; version="${range;[6,+)}", * This means use literal '6' as

Re: Can you make the maven bundle plugin use maven version ranges?

Bnd (and by extension the maven-bundle-plugin) uses semantic versions to infer import ranges, based on the actual version that was compiled against. If you build against version 8.0.0 of an API then we have no way to know that you are also compatible with versions 7.0.0 and 6.0.0. In fact it

Can you make the maven bundle plugin use maven version ranges?

Hello everyone. I am trying to make the Maven Bundle Plugin use a version range i have defined in the POM of my project. Basically a project of mine has a small wicket module which i know works through wicket 6-8. So i have defined the following dependency: org.apache.wicket