Nice trick! Thx On Fri, Jan 16, 2015 at 9:00 PM, BJ Hargrave <[email protected]> wrote:
> I mean: run that code and see what the returned string is. You can use the > toFilterString() method on VersionRange to compute the proper filter string > for any version range. > -- > > *BJ Hargrave* > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/> > *[email protected]* <[email protected]> > > office: +1 386 848 1781 > mobile: +1 386 848 3788 > > > > > > From: Raymond Auge <[email protected]> > To: OSGi Developer Mail List <[email protected]> > Date: 2015/01/16 20:34 > Subject: Re: [osgi-dev] filter syntax for version range with > exclusive upper bound > Sent by: [email protected] > ------------------------------ > > > > I should have clarified in a Require-Capability header filter syntax. > > - Ray > > > On Fri, Jan 16, 2015 at 8:31 PM, BJ Hargrave <*[email protected]* > <[email protected]>> wrote: > new VersionRange("[1.0,2.0)").toFilterString() > -- > > *BJ Hargrave* > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/> > *[email protected]* <[email protected]> > > office: *+1 386 848 1781* <%2B1%20386%20848%201781> > mobile: *+1 386 848 3788* <%2B1%20386%20848%203788> > > > > > > From: Raymond Auge <*[email protected]* > <[email protected]>> > To: OSGi Developer Mail List <*[email protected]* > <[email protected]>> > Date: 2015/01/16 20:16 > Subject: [osgi-dev] filter syntax for version range with exclusive > upper bound > Sent by: *[email protected]* > <[email protected]> > ------------------------------ > > > > > Is this the best way to express this: > > (&(version>=1.0)(version<=2.0)(!(version=2.0))) > > > There does not appear to be a only a < in the filter syntax. > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/> > (@Liferay) > Board Member & EEG Co-Chair, *OSGi Alliance* <http://osgi.org/> > (@OSGiAlliance)_______________________________________________ > OSGi Developer Mail List > *[email protected]* <[email protected]> > *https://mail.osgi.org/mailman/listinfo/osgi-dev* > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > _______________________________________________ > OSGi Developer Mail List > *[email protected]* <[email protected]> > *https://mail.osgi.org/mailman/listinfo/osgi-dev* > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com/> > (@Liferay) > Board Member & EEG Co-Chair, *OSGi Alliance* <http://osgi.org/> > (@OSGiAlliance)_______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
