Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » No suitable provider for component org.eclipse.license:eclipse.feature
No suitable provider for component org.eclipse.license:eclipse.feature [message #1666063] Wed, 11 March 2015 14:20 Go to next message
Vlad Dumitrescu is currently offline Vlad DumitrescuFriend
Messages: 421
Registered: July 2009
Location: Gothenburg
Senior Member
Hi!

I'm at my wit's end... My Buckminster-based build worked nicely, until today when I updated my Eclipse installation to 4.4.2. I get the error below, but that repository contains a feature with a matching version number.

Buckminster hasn't changed, it's 1.6.0. It feels very disturbing to have a setup that suddenly doesn't work anymore. Additionaly, there is no clue where the problem is.

For some reason, I couldn't revert my installation, I'm working on that to see if the problem was caused by the upgrade or something else. In the meantime, any suggestions on how to find out what is going on? This isn't the first time something like this happens to me, but I never know which ones of my desperate attempts at recovery worked... Why is Buckminster so sensitive to the environment?

best regards,
Vlad

ERROR   [0007] : No suitable provider for component org.eclipse.license:eclipse.feature/[1.0.1.qualifier,1.0.1.qualifier] was found in searchPath eclipse
    ERROR   [0007] : Rejecting provider p2({0}[http://download.eclipse.org/cbi/updates/license/]): No component match was found
Re: No suitable provider for component org.eclipse.license:eclipse.feature [message #1666180 is a reply to message #1666063] Wed, 11 March 2015 15:21 Go to previous messageGo to next message
Ed Willink is currently offline Ed WillinkFriend
Messages: 6002
Registered: July 2009
Senior Member
Hi

I suspect you had an accidentally working solution, that stopped
accidentally working.

My recollection is that the org.eclipse.license versioning has never
worked with Buckminster. Consequently OCL and QVTd builds at least get
org.eclipse.license from

<rm:locator pattern="^org\.eclipse\.license.*"
searchPathRef="license-source-code"/>

<rm:searchPath name="license-source-code">
<rm:provider componentTypes="eclipse.feature" readerType="git">
<rm:property key="git.remote.uri"
value="/gitroot/cbi/org.eclipse.license.git"/>
<rm:property key="git.auto.fetch" value="true"/>
<rm:uri format="{0},{1}">
<bc:propertyRef key="git.license.local.repository.location"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432841
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255

Regards

Ed Willink

On 11/03/2015 14:20, Vlad Dumitrescu wrote:
> Hi!
>
> I'm at my wit's end... My Buckminster-based build worked nicely, until
> today when I updated my Eclipse installation to 4.4.2. I get the error
> below, but that repository contains a feature with a matching version
> number.
>
> Buckminster hasn't changed, it's 1.6.0. It feels very disturbing to
> have a setup that suddenly doesn't work anymore. Additionaly, there is
> no clue where the problem is.
> For some reason, I couldn't revert my installation, I'm working on
> that to see if the problem was caused by the upgrade or something
> else. In the meantime, any suggestions on how to find out what is
> going on? This isn't the first time something like this happens to me,
> but I never know which ones of my desperate attempts at recovery
> worked... Why is Buckminster so sensitive to the environment?
>
> best regards,
> Vlad
>
> ERROR [0007] : No suitable provider for component
> org.eclipse.license:eclipse.feature/[1.0.1.qualifier,1.0.1.qualifier]
> was found in searchPath eclipse
> ERROR [0007] : Rejecting provider
> p2({0}[http://download.eclipse.org/cbi/updates/license/]): No
> component match was found
>
Re: No suitable provider for component org.eclipse.license:eclipse.feature [message #1666818 is a reply to message #1666180] Wed, 11 March 2015 21:39 Go to previous messageGo to next message
Vlad Dumitrescu is currently offline Vlad DumitrescuFriend
Messages: 421
Registered: July 2009
Location: Gothenburg
Senior Member
Thanks Ed,

I'm not sure what the problem is, but at home with an Eclipse installation that I think is identical, everything works fine. I'll check the configurations to see if there is a difference.

regards,
Vlad
Re: No suitable provider for component org.eclipse.license:eclipse.feature [message #1694234 is a reply to message #1666180] Sun, 03 May 2015 08:54 Go to previous messageGo to next message
Erdal Karaca is currently offline Erdal KaracaFriend
Messages: 842
Registered: July 2009
Senior Member
Hi Ed,
I have tried the buckminster instructions you have provided, but getting the following errors:

ERROR   [0002] : No suitable provider for component org.eclipse.license:eclipse.feature was found in searchPath license-source-code
    ERROR   [0002] : Rejecting provider git({0},{1}[null,org.eclipse.license]): No component match was found
      ERROR   Git repository path "null" is not absolute


The feature references the shared feature as follows:

      license-feature="org.eclipse.license"
      license-feature-version="0.0.0"


I am on build.eclipse.org.

Do you have any hints?

Thanks.

Ed Willink wrote on Wed, 11 March 2015 16:21
Hi

I suspect you had an accidentally working solution, that stopped
accidentally working.

My recollection is that the org.eclipse.license versioning has never
worked with Buckminster. Consequently OCL and QVTd builds at least get
org.eclipse.license from

<rm:locator pattern="^org\.eclipse\.license.*"
searchPathRef="license-source-code"/>

<rm:searchPath name="license-source-code">
<rm:provider componentTypes="eclipse.feature" readerType="git">
<rm:property key="git.remote.uri"
value="/gitroot/cbi/org.eclipse.license.git"/>
<rm:property key="git.auto.fetch" value="true"/>
<rm:uri format="{0},{1}">
<bc:propertyRef key="git.license.local.repository.location"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432841
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255

Regards

Ed Willink

On 11/03/2015 14:20, Vlad Dumitrescu wrote:
> Hi!
>
> I'm at my wit's end... My Buckminster-based build worked nicely, until
> today when I updated my Eclipse installation to 4.4.2. I get the error
> below, but that repository contains a feature with a matching version
> number.
>
> Buckminster hasn't changed, it's 1.6.0. It feels very disturbing to
> have a setup that suddenly doesn't work anymore. Additionaly, there is
> no clue where the problem is.
> For some reason, I couldn't revert my installation, I'm working on
> that to see if the problem was caused by the upgrade or something
> else. In the meantime, any suggestions on how to find out what is
> going on? This isn't the first time something like this happens to me,
> but I never know which ones of my desperate attempts at recovery
> worked... Why is Buckminster so sensitive to the environment?
>
> best regards,
> Vlad
>
> ERROR [0007] : No suitable provider for component
> org.eclipse.license:eclipse.feature/[1.0.1.qualifier,1.0.1.qualifier]
> was found in searchPath eclipse
> ERROR [0007] : Rejecting provider
> p2({0}[http://download.eclipse.org/cbi/updates/license/]): No
> component match was found
>
Re: No suitable provider for component org.eclipse.license:eclipse.feature [message #1694235 is a reply to message #1694234] Sun, 03 May 2015 09:49 Go to previous message
Erdal Karaca is currently offline Erdal KaracaFriend
Messages: 842
Registered: July 2009
Senior Member
It seems that I have missed to set up the checkout directory (propertyRef git.license.local.repository.location)

Thanks, Ed for the instructions. They have helped me to make use of the shared licence feature using buckminster build.

Erdal Karaca wrote on Sun, 03 May 2015 10:54
Hi Ed,
I have tried the buckminster instructions you have provided, but getting the following errors:

ERROR   [0002] : No suitable provider for component org.eclipse.license:eclipse.feature was found in searchPath license-source-code
    ERROR   [0002] : Rejecting provider git({0},{1}[null,org.eclipse.license]): No component match was found
      ERROR   Git repository path "null" is not absolute


The feature references the shared feature as follows:

      license-feature="org.eclipse.license"
      license-feature-version="0.0.0"


I am on build.eclipse.org.

Do you have any hints?

Thanks.

Previous Topic:Excluding Jars from signing
Next Topic:Questions about signing
Goto Forum:
  


Current Time: Thu Aug 16 21:54:33 GMT 2018

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

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

Back to the top