Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Buckminster fails to find bundles
Buckminster fails to find bundles [message #520344] Thu, 11 March 2010 21:50 Go to next message
Alex Kravets is currently offline Alex Kravets
Messages: 380
Registered: November 2009
Senior Member
Hello,

During my build Buckminster fails to find some bundles which are pretty much the same in nature as other bundles that have been successfully located. I even created a word by word locator just to find these bundles, but nothing helps. This is the error I am getting:
Quote:

...
org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1 4.v200701080905]: No provider was found that could resolve the request
ERROR [0000] : No suitable provider for component org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1 4.v200701080905] was found in resourceMap file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/ totaltrader/build/com.totaltrader.site/site.rmap
ERROR [0000] : No suitable provider for component org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1 4.v200701080905] was found in searchPath totaltrader
ERROR [0000] : Resolution attempt ended with exception: Provider local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac e/totaltrader/org.apache.log4j): Missing CSpec source required by component type eclipse.feature
ERROR Provider local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac e/totaltrader/org.apache.log4j): Missing CSpec source required by component type eclipse.feature
...
org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0. 0.v200701071427]: No provider was found that could resolve the request
ERROR [0000] : No suitable provider for component org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0. 0.v200701071427] was found in resourceMap file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/ totaltrader/build/com.totaltrader.site/site.rmap
ERROR [0000] : No suitable provider for component org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0. 0.v200701071427] was found in searchPath totaltrader
ERROR [0000] : Resolution attempt ended with exception: Provider local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac e/totaltrader/org.apache.commons): Missing CSpec source required by component type eclipse.feature
ERROR Provider local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac e/totaltrader/org.apache.commons): Missing CSpec source required by component type eclipse.feature



What is the nature of this error?

Also, how does Buckminster decide what is the eclipse.feature and osgi.bundle. I have two similar bundles org.jdom and or.apache.log4j, first is treated as bundle and second as feature.

thanks,
Alex

[Updated on: Thu, 11 March 2010 21:56]

Report message to a moderator

Re: Buckminster fails to find bundles [message #520406 is a reply to message #520344] Thu, 11 March 2010 23:58 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Hi Alex,
From the looks of it, the resolver isn't trying to find bundles. It's looking for features. It fails because it doesn't
find the feature.xml at the specified locations.

HTH,
- thomas


On 03/12/2010 03:50 AM, Alex wrote:
> Hello,
>
> During my build Buckminster fails to find some bundles which are pretty
> much the same in nature as other bundles that have been successfully
> located. I even created a word by word locator just to find these
> bundles, but nothing helps. This is the error I am getting:
> Quote:
>> ...
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905]: No provider was found that could resolve the request
>> ERROR [0000] : No suitable provider for component
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905] was found in resourceMap
>> file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/
>> totaltrader/build/com.totaltrader.site/site.rmap
>> ERROR [0000] : No suitable provider for component
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905] was found in searchPath totaltrader
>> ERROR [0000] : Resolution attempt ended with exception: Provider
>> local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.log4j): Missing CSpec source required by
>> component type eclipse.feature
>> ERROR Provider local(
>> file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.log4j): Missing CSpec source required by
>> component type eclipse.feature
>> ...
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427]: No provider was found that could resolve the request
>> ERROR [0000] : No suitable provider for component
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427] was found in resourceMap
>> file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/
>> totaltrader/build/com.totaltrader.site/site.rmap
>> ERROR [0000] : No suitable provider for component
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427] was found in searchPath totaltrader
>> ERROR [0000] : Resolution attempt ended with exception: Provider
>> local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.commons): Missing CSpec source required by
>> component type eclipse.feature
>> ERROR Provider local(
>> file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.commons): Missing CSpec source required by
>> component type eclipse.feature
>
>
> What is the nature of this error?
>
> thanks,
> Alex
>
Re: Buckminster fails to find bundles [message #520407 is a reply to message #520344] Thu, 11 March 2010 23:58 Go to previous messageGo to next message
Achim Demelt is currently offline Achim Demelt
Messages: 160
Registered: July 2009
Senior Member
Hi Alex,

It looks to me like the component type is wrong. The error message says:

org.apache.log4j:eclipse.feature/...: No provider was found

I think that there is no feature for org.apache.log4j, only a bundle. The
same applies to the other artifacts that cannot be resolved. Can you check
your dependencies?

Cheers,
Achim

Alex wrote:

> Hello,
>
> During my build Buckminster fails to find some bundles which are pretty
> much the same in nature as other bundles that have been successfully
> located. I even created a word by word locator just to find these bundles,
> but nothing helps. This is the error I am getting: Quote:
>> ...
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905]: No provider was found that could resolve the request
>> ERROR [0000] : No suitable provider for component
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905] was found in resourceMap
>> file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/
>> totaltrader/build/com.totaltrader.site/site.rmap
>> ERROR [0000] : No suitable provider for component
>> org.apache.log4j:eclipse.feature/[1.2.14.v200701080905,1.2.1
>> 4.v200701080905] was found in searchPath totaltrader
>> ERROR [0000] : Resolution attempt ended with exception: Provider
>> local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.log4j): Missing CSpec source required by
>> component type eclipse.feature
>> ERROR Provider local(
>> file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.log4j): Missing CSpec source required by
>> component type eclipse.feature
>> ...
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427]: No provider was found that could resolve the request
>> ERROR [0000] : No suitable provider for component
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427] was found in resourceMap
>> file:/home/akravets2/.hudson/jobs/buckminster.job/workspace/
>> totaltrader/build/com.totaltrader.site/site.rmap
>> ERROR [0000] : No suitable provider for component
>> org.apache.commons:eclipse.feature/[1.0.0.v200701071427,1.0.
>> 0.v200701071427] was found in searchPath totaltrader
>> ERROR [0000] : Resolution attempt ended with exception: Provider
>> local( file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.commons): Missing CSpec source required by
>> component type eclipse.feature
>> ERROR Provider local(
>> file:///home/akravets2/.hudson/jobs/buckminster.job/workspac
>> e/totaltrader/org.apache.commons): Missing CSpec source required by
>> component type eclipse.feature
>
>
> What is the nature of this error?
>
> thanks,
> Alex
Re: Buckminster fails to find bundles [message #520501 is a reply to message #520407] Fri, 12 March 2010 11:13 Go to previous messageGo to next message
Alex Kravets is currently offline Alex Kravets
Messages: 380
Registered: November 2009
Senior Member
Thanks Thomas and Achim,

Yeah, that's what I thought, but wasn't sure completely.

thanks,
Alex

[Updated on: Fri, 12 March 2010 13:26]

Report message to a moderator

Re: Buckminster fails to find bundles [message #520549 is a reply to message #520501] Fri, 12 March 2010 09:22 Go to previous messageGo to next message
Achim Demelt is currently offline Achim Demelt
Messages: 160
Registered: July 2009
Senior Member
Hi Alex,

The log4j bundle itself is ok. It's rather the component that references it
seems to look for a *feature* named org.apache.log4j, rather than a bundle.
Do you have a CSPEC somewhere that depends on org.apache.log4j?

Cheers,
Achim


Alex wrote:

> Thanks Thomas and Achim,
>
> Yeah, that's what I thought, but wasn't sure completely.
>
> May be you can take a look at my manifest to see what's wrong?
>
>
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: %pluginName
> Bundle-SymbolicName: org.apache.log4j
> Bundle-Version: 1.2.14.v200701080905
> Bundle-Vendor: %providerName
> Bundle-Localization: plugin
> Export-Package: org.apache.log4j;version="1.2.14",
> org.apache.log4j.chainsaw;version="1.2.14",
> org.apache.log4j.config;version="1.2.14",
> org.apache.log4j.helpers;version="1.2.14",
> org.apache.log4j.jdbc;version="1.2.14",
> org.apache.log4j.jmx;version="1.2.14",
> org.apache.log4j.lf5;version="1.2.14",
> org.apache.log4j.lf5.util;version="1.2.14",
> org.apache.log4j.lf5.viewer;version="1.2.14",
> org.apache.log4j.lf5.viewer.categoryexplorer;version="1.2.14 ",
> org.apache.log4j.lf5.viewer.configure;version="1.2.14",
> org.apache.log4j.net;version="1.2.14",
> org.apache.log4j.nt;version="1.2.14",
> org.apache.log4j.or;version="1.2.14",
> org.apache.log4j.or.jms;version="1.2.14",
> org.apache.log4j.or.sax;version="1.2.14",
> org.apache.log4j.spi;version="1.2.14",
> org.apache.log4j.varia;version="1.2.14",
> org.apache.log4j.xml;version="1.2.14"
> Bundle-ClassPath: log4j-1.2.14.jar
> Bundle-RequiredExecutionEnvironment: J2SE-1.4
>
>
> thanks,
> Alex
Re: Buckminster fails to find bundles [message #520553 is a reply to message #520344] Fri, 12 March 2010 14:31 Go to previous message
Alex Kravets is currently offline Alex Kravets
Messages: 380
Registered: November 2009
Senior Member
Hi Achim,

Yes, that was exactly the problem, and after fixing it everything worked perfectly. Buckminster rocks!

thanks for your help!
Alex
Previous Topic:Buckminster and fragments and unit tests
Next Topic:buckminster headless subversive support not working
Goto Forum:
  


Current Time: Fri Aug 29 14:29:30 EDT 2014

Powered by FUDForum. Page generated in 0.02171 seconds