Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Dependency resolution - too broad?
Dependency resolution - too broad? [message #653422] Wed, 09 February 2011 12:27 Go to next message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
Recently I did a "resolve and materialize" for a feature project, and was surprised to see a lot more plugins checked out than I expected.

The reason turned out to be that one of the plugins that my feature required had an old .product file in it (.product files are normally put in feature projects, not plugins, but anyhow ...). The bad .product file had a whole lot of extra plugin names in it. I have also seen similar behavior with .launch configurations.

It seems that when Buckminster determines dependencies for Eclipse projects, it looks in any .launch or .product file that it comes across, and any dependencies in there are applied to the enclosing component.

This is, I guess, by design - Buckminster is using Eclipse-maintained metadata as advertised. However, it can be annoying, particularly with .launch configurations, since our developers sometimes check in bad configrations, on the grounds that they are only testing aids anyhow.

Is there a way I can tell Buckminster to avoid .launch and/or .product files when examining existing metadata? Maybe something in a CSPEX?

Re: Dependency resolution - too broad? [message #653436 is a reply to message #653422] Wed, 09 February 2011 13:16 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3228
Registered: July 2009
Senior Member
Hi Matthew,

To my knowledge, Buckminster doesn't look at .launch configurations. .products yes, but not .launch.

The easiest way to exclude .product from the search is to move it into a folder. Buckminster will only look in the root.
Alternatively, you can add a .cspex in adjacent to the .product file where you remove the unwanted dependencies using an
<alterDependencies> element with <remove name=""> sub elements.

- thomas

On 2011-02-09 18:27, Matthew Webber wrote:
> Recently I did a "resolve and materialize" for a feature project, and was surprised to see a lot more plugins checked
> out than I expected.
>
> The reason turned out to be that one of the plugins that my feature required had an old .product file in it (.product
> files are normally put in feature projects, not plugins, but anyhow ...). The bad .product file had a whole lot of extra
> plugin names in it. I have also seen similar behavior with .launch configurations.
>
> It seems that when Buckminster determines dependencies for Eclipse projects, it looks in any .launch or .product file
> that it comes across, and any dependencies in there are applied to the enclosing component.
>
> This is, I guess, by design - Buckminster is using Eclipse-maintained metadata as advertised. However, it can be
> annoying, particularly with .launch configurations, since our developers sometimes check in bad configrations, on the
> grounds that they are only testing aids anyhow.
>
> Is there a way I can tell Buckminster to avoid .launch and/or .product files when examining existing metadata? Maybe
> something in a CSPEX?
>
>
Re: Dependency resolution - too broad? [message #653575 is a reply to message #653436] Thu, 10 February 2011 05:20 Go to previous message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
Thanks, that will work for me. I just noticed that this is actually described in the BuckyBook (page 94 in v0.8).
Previous Topic:setting the time zone for buckminster?
Next Topic:Resolve: Update plugins already present
Goto Forum:
  


Current Time: Wed Aug 20 06:50:24 EDT 2014

Powered by FUDForum. Page generated in 0.01395 seconds