Eclipse Community Forums: Buckminster » Unnecessary searching for source bundles

Help

Home

Home » Archived » Buckminster » Unnecessary searching for source bundles

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

Unnecessary searching for source bundles [message #925043]

Thu, 27 September 2012 10:27

Matthew Webber

Messages: 198
Registered: December 2010

Senior Member

I've noticed some strange behavior when I materialize a CQuery. The CQuery correctly resolves a component a.b.c (type osgi.bundle) by finding it in a repository (git or subversion).

It then goes looking for another component, called a.b.c.source. I presume that this is triggered by my setting buckminster.download.source to true. There is no such named component, which does not fail the CQuery, but does slow the resolution down since it wastes time looking in various places.

My question is, WHY does Buckminster looks for a .source bundle? At that point, it has already found the source code in a repository. My understanding is that the search for matching .source only makes sense for .jars in the target platform, not for components that are already source.

Have I misunderstood how it is supposed to work, or is this a bug?

This is Eclipse 3.7.2 IDE with the matching Buckminster version.

Thanks
Matthew

Report message to a moderator

Re: Unnecessary searching for source bundles [message #925224 is a reply to message #925043]

Thu, 27 September 2012 14:03

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

I agree. It doesn't make sense to search for source bundles when what it already found is in fact, the source. Can you
please enter a bugzilla for this?

Thanks,
- thomas

On 2012-09-27 12:27, Matthew Webber wrote:
> I've noticed some strange behavior when I materialize a CQuery. The CQuery correctly resolves a component a.b.c (type
> osgi.bundle) by finding it in a repository (git or subversion).
>
> It then goes looking for another component, called a.b.c.source. I presume that this is triggered by my setting
> buckminster.download.source to true. There is no such named component, which does not fail the CQuery, but does slow the
> resolution down since it wastes time looking in various places.
>
> My question is, WHY does Buckminster looks for a .source bundle? At that point, it has already found the source code in
> a repository. My understanding is that the search for matching .source only makes sense for .jars in the target
> platform, not for components that are already source.
>
> Have I misunderstood how it is supposed to work, or is this a bug?
>
> This is Eclipse 3.7.2 IDE with the matching Buckminster version.
>
> Thanks
> Matthew
>

Report message to a moderator