Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster dev » Re: causes failure
Re: causes failure [message #722731] Tue, 06 September 2011 15:10
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-09-06 16:31, Alan Underwood wrote:
> Hi, Thomas
> I thought it might have been my misunderstanding of what source="true" means. However, I still have a problem resolving
> the binary plug-in with when there is no source. I've looked at the
> CSpecBuilder.addSourceDependency() method, which adds the source plugin dependency to the cspec and sets a filter on
> that dependency to make it optional (I presume). The filter is:
> (&(!(eclipse.p2.optional=false)))
> But when it comes to resolving the child node (the .source plug-in) I don't think the filter applied to the dependency
> is checked - I think it might be using the filter in the context it takes from the binary plug-in which is not optional,
> but I find it difficult to follow the code.
> I have checked the binary plug-in and it has no dependency on .source, the .source dependency is added by the
> addSourceDependency() method.
> Any ideas? Where in the code does the resolver check for filters such as eclipse.p2.optional?
The eclipse.p2.optional filter is generated synthetically when features or plug-ins have optional requirements. The
Buckminster resolver will attempt to resolve such dependencies but will be forgiving if they are not found.

What kind of errors do you see and when?

- thomas
Previous Topic:Re: [buckminster-dev] problem replacing qualifiers with lastRevision and add suffix for features
Next causes failure
Goto Forum:

Current Time: Thu Oct 21 22:54:29 GMT 2021

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

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

Back to the top