Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » version range substitution in MANIFEST.MF
version range substitution in MANIFEST.MF [message #956921] Wed, 24 October 2012 22:28 Go to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1417
Registered: July 2009
Senior Member
Hi

I noted that when I create a p2.site with buckminster action, if a
bundle in its MANIFEST.MF has a lowerbound then in the MANIFEST.MF of
the generated jar that version range is kept, but if there is no version
range in the original MANIFEST.MF, then in the generated MANIFEST.MF a
brand new version range is automatically created:

- lowerbound: the version of the required bundle as in the current
target platform, say 1.x.y
- upperbound: the next major version, thus 2.0.0 in this example

is this the normal behavior coming from p2 or somewhere else?

thanks in advance
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Re: version range substitution in MANIFEST.MF [message #957674 is a reply to message #956921] Thu, 25 October 2012 12:00 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
This is the default behaviour. The behaviour can be controlled using
properties. You can find more info on the documentation issue here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=309147#c2

We have a long backlog on documentation issues currently.

- thomas


On 2012-10-25 00:28, Lorenzo Bettini wrote:
> Hi
>
> I noted that when I create a p2.site with buckminster action, if a
> bundle in its MANIFEST.MF has a lowerbound then in the MANIFEST.MF of
> the generated jar that version range is kept, but if there is no version
> range in the original MANIFEST.MF, then in the generated MANIFEST.MF a
> brand new version range is automatically created:
>
> - lowerbound: the version of the required bundle as in the current
> target platform, say 1.x.y
> - upperbound: the next major version, thus 2.0.0 in this example
>
> is this the normal behavior coming from p2 or somewhere else?
>
> thanks in advance
> Lorenzo
>
Re: version range substitution in MANIFEST.MF [message #960465 is a reply to message #957674] Sat, 27 October 2012 14:03 Go to previous message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1417
Registered: July 2009
Senior Member
On 10/25/2012 02:00 PM, Thomas Hallgren wrote:
> This is the default behaviour. The behaviour can be controlled using
> properties. You can find more info on the documentation issue here:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=309147#c2
>

Thanks Thomas

This concerns only required bundles where I haven't made no version
range explicitly, right?

Please, let me check whether I understand:

*pde.match.rule.bundle*
Defines the match rule used for the "Require-Bundle" header.
Default: compatible

*pde.match.rule.bundle.lower*
Defines an additional rule for the lower bound of the ranges generated
for the "Require-Bundle" header.
Default: equivalent

"The lower match rule enables fine grained control of the lower bound.
This only makes sense if it is set to a rule that is more stringent then
the setting for the main match rule."

since the "lower" rule is more stringent by default, then the generated
ranges will be

1.2.3.abc -> [1.2.0,2.0.0)

right?

However, 1.2.3.abc refers to the version in the target platform.

> We have a long backlog on documentation issues currently.
>

do you mean that the bucky book is becoming obsolete? Can I help in
some way?

cheers
Lorenzo

> - thomas
>
>
> On 2012-10-25 00:28, Lorenzo Bettini wrote:
>> Hi
>>
>> I noted that when I create a p2.site with buckminster action, if a
>> bundle in its MANIFEST.MF has a lowerbound then in the MANIFEST.MF of
>> the generated jar that version range is kept, but if there is no version
>> range in the original MANIFEST.MF, then in the generated MANIFEST.MF a
>> brand new version range is automatically created:
>>
>> - lowerbound: the version of the required bundle as in the current
>> target platform, say 1.x.y
>> - upperbound: the next major version, thus 2.0.0 in this example
>>
>> is this the normal behavior coming from p2 or somewhere else?
>>
>> thanks in advance
>> Lorenzo
>>
>


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
Previous Topic:Building product for Eclipse 3.7+
Next Topic:[solved] Can't install emma.headless
Goto Forum:
  


Current Time: Fri Dec 19 01:41:30 GMT 2014

Powered by FUDForum. Page generated in 0.02329 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software