Eclipse Community Forums: B3 » r10682 - prerequisites

Help

Home

Home » Archived » B3 » r10682 - prerequisites - requirement on interface

Show: Today's Messages :: Show Polls :: Message Navigator

r10682 - prerequisites - requirement on interface [message #487826]

Thu, 24 September 2009 14:09

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

Added "propertyName" to IRequirment, to make a prerequisite capable of
referencing a property in the ICapability returned as a resolution of
the requirement.

This was done since a requirement may be to any capability, and we do
not want to expose every part name as a capability since all units of a
particular "type" would then have the exact same capability - so far
better to have a requirement on the "type"/"interface".

In addition to this change, we need to have the capability to express a
requirement on a particular interface. Not yet clear how this should be
done. The current version of the models express requirements in terms of
"name in namespace and version". b3 needs an additional layer to that -
since a metadata translator is involved. Different versions of metadata
translators may produce different interfaces over time.

It may be enough to express this as meta requirements - i.e. that a
metadata translator providing a particular version of the translator API
is required by a build unit.

Regards
- henrik

Report message to a moderator

Re: r10682 - prerequisites - requirement on interface [message #487837 is a reply to message #487826]

Thu, 24 September 2009 14:23

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

On 09/24/2009 04:09 PM, Henrik Lindberg wrote:
> Added "propertyName" to IRequirment, to make a prerequisite capable of
> referencing a property in the ICapability returned as a resolution of
> the requirement.
>
> This was done since a requirement may be to any capability, and we do
> not want to expose every part name as a capability since all units of a
> particular "type" would then have the exact same capability - so far
> better to have a requirement on the "type"/"interface".
>
Not sure I understand. Why would you ever want to reference a property of something that has been resolved?

- thomas

Report message to a moderator

Re: r10682 - prerequisites - requirement on interface [message #487849 is a reply to message #487837]

Thu, 24 September 2009 14:45

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

- You require a capability
- Someone provides this capability
- The resolution result is the thing that provides the capability
- There is nothing that tells you (or anyone) how this particular
capability is obtained
- That is the "propertyName" - a generalizaion for "partName"
- So if you want build unit A's part X, you would have a requirement on
org.eclipse.b3.unit, A, and set the property to X
- i.e. 'X' is not part of the requirement, but it is how you pick up the
prerequisite contribution

Changed the name from "property" to "memberName" after chat discussion.
(r10685)
- henrik

Thomas Hallgren wrote:
> On 09/24/2009 04:09 PM, Henrik Lindberg wrote:
>> Added "propertyName" to IRequirment, to make a prerequisite capable of
>> referencing a property in the ICapability returned as a resolution of
>> the requirement.
>>
>> This was done since a requirement may be to any capability, and we do
>> not want to expose every part name as a capability since all units of a
>> particular "type" would then have the exact same capability - so far
>> better to have a requirement on the "type"/"interface".
>>
> Not sure I understand. Why would you ever want to reference a property
> of something that has been resolved?
>
> - thomas

Report message to a moderator