Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Feature dependencies and pde.match.rule
Feature dependencies and pde.match.rule [message #554079] Fri, 20 August 2010 05:32 Go to next message
Peter Kullmann is currently offline Peter KullmannFriend
Messages: 240
Registered: July 2009
Senior Member
Hi,

I have been reading about the way buckminster creates version ranges
from feature dependencies (includes) and how these ranges are determined
with the following two properties in build.properties of the feature, eg:

pde.match.rule.default = greaterOrEqual
pde.match.rule.retain.lower = false

How is this supposed to work? Given a feature that includes another
feature with version 1.0.0.foo. I selected Buckminster / View CSpec...
for the feature and I can see that all dependencies have version ranges
like this: [1.0.0.foo,1.0.0.foo], ie perfect match. The pde.match.rule
properties in build.properties do not make any effect.
I also tried to resolve the feature and am getting the errors that there
is no provider for the dependency/[1.0.0.foo,1.0.0.foo]...

Regards
Peter
Re: Feature dependencies and pde.match.rule [message #554103 is a reply to message #554079] Fri, 20 August 2010 07:52 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
The feature ranges are generated at build time so you won't see any changes in the cspec. There's no way of knowing the
actual final range until every other feature has been built (or generated).

- thomas



On 08/20/2010 07:32 AM, Peter Kullmann wrote:
> Hi,
>
> I have been reading about the way buckminster creates version ranges
> from feature dependencies (includes) and how these ranges are determined
> with the following two properties in build.properties of the feature, eg:
>
> pde.match.rule.default = greaterOrEqual
> pde.match.rule.retain.lower = false
>
> How is this supposed to work? Given a feature that includes another
> feature with version 1.0.0.foo. I selected Buckminster / View CSpec...
> for the feature and I can see that all dependencies have version ranges
> like this: [1.0.0.foo,1.0.0.foo], ie perfect match. The pde.match.rule
> properties in build.properties do not make any effect.
> I also tried to resolve the feature and am getting the errors that there
> is no provider for the dependency/[1.0.0.foo,1.0.0.foo]...
>
> Regards
> Peter
Re: Feature dependencies and pde.match.rule [message #554173 is a reply to message #554103] Fri, 20 August 2010 12:29 Go to previous message
Peter Kullmann is currently offline Peter KullmannFriend
Messages: 240
Registered: July 2009
Senior Member
Does this mean that feature ranges are not usable for (target)
resolution and materialization. Eg I would like to specify
org.eclipse.platform 3.5.2 in the feature that describes my target. But
that would not work because during resolution these versions are used
like [3.5.2,3.5.2]. So it seems that I either have to specify exact
versions with qualifiers (which is possible, of course) or that I would
use a buckminster component instead of a feature to describe the target.

Regards,
Peter


Thomas Hallgren schrieb:
> The feature ranges are generated at build time so you won't see any
> changes in the cspec. There's no way of knowing the actual final range
> until every other feature has been built (or generated).
>
> - thomas
>
>
>
> On 08/20/2010 07:32 AM, Peter Kullmann wrote:
>> Hi,
>>
>> I have been reading about the way buckminster creates version ranges
>> from feature dependencies (includes) and how these ranges are determined
>> with the following two properties in build.properties of the feature, eg:
>>
>> pde.match.rule.default = greaterOrEqual
>> pde.match.rule.retain.lower = false
>>
>> How is this supposed to work? Given a feature that includes another
>> feature with version 1.0.0.foo. I selected Buckminster / View CSpec...
>> for the feature and I can see that all dependencies have version ranges
>> like this: [1.0.0.foo,1.0.0.foo], ie perfect match. The pde.match.rule
>> properties in build.properties do not make any effect.
>> I also tried to resolve the feature and am getting the errors that there
>> is no provider for the dependency/[1.0.0.foo,1.0.0.foo]...
>>
>> Regards
>> Peter
>
Previous Topic:Revision number in create.product.zip
Next Topic:org.eclipse.jdt.core issue - groovy support
Goto Forum:
  


Current Time: Thu Mar 28 09:17:23 GMT 2024

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

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

Back to the top