Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » "No suitable provider" error with svn provider
"No suitable provider" error with svn provider [message #556027] Mon, 30 August 2010 15:24 Go to next message
Tomsen  is currently offline Tomsen Friend
Messages: 42
Registered: July 2010
Member
Hi all,
I try to adapt the Buckminster Mailapp Buckminster files to my application and keep getting the following errors when trying to "Resolve to Wizard" my developer.cquery

!ENTRY org.eclipse.buckminster.core 4 293 2010-08-30 14:57:08.046
!MESSAGE ERROR   [0001] : No suitable provider for component de.softproject.xe.standalone.feature:eclipse.feature was found in resourceMap file:/C:/SVN/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.releng/eclipse.rmap
  ERROR   [0001] : No suitable provider for component de.softproject.xe.standalone.feature:eclipse.feature was found in searchPath de.softproject.xe
    ERROR   [0001] : Filter (&(target.nl=en)(target.os=win32)(target.ws=win32)(|(target.arch=ia64)(target.arch=ia64_32)(target.arch=x86)(target.arch=x86_64))) does not match the current property set


Not sure what part the last line plays. I think I have a proper match for feature
de.softproject.xe.standalone.feature
in my rmap which looks like
...
  <rm:locator pattern="^de\.softproject\.xe(\..+)?" searchPathRef="de.softproject.xe"/>
...
  <rm:searchPath name="de.softproject.xe">
    <rm:provider componentTypes="osgi.bundle,eclipse.feature,buckminster" 
    			 readerType="svn"
    			 mutable="true"
    			 source="true">
      <rm:uri format="https://{0}:{1}@80.xxx.xxxx.xxx/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/{2}">
        <bc:propertyRef key="svn.user"/>
        <bc:propertyRef key="svn.password"/>
        <bc:propertyRef key="buckminster.component"/>
      </rm:uri>
    </rm:provider>
  </rm:searchPath>


I have Target.* set to meaningful values.
Re: "No suitable provider" error with svn provider [message #556063 is a reply to message #556027] Mon, 30 August 2010 17:17 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Do you have all target.xxx set to '*' ? Even target.nl?

- thomas

On 08/30/2010 05:24 PM, Tomsen wrote:
> Hi all,
> I try to adapt the Buckminster Mailapp Buckminster files to my
> application and keep getting the following errors when trying to
> "Resolve to Wizard" my developer.cquery
>
> !ENTRY org.eclipse.buckminster.core 4 293 2010-08-30 14:57:08.046
> !MESSAGE ERROR [0001] : No suitable provider for component
> de.softproject.xe.standalone.feature:eclipse.feature was found in
> resourceMap
> file:/C:/SVN/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.soft project.xe.standalone.releng/eclipse.rmap
>
> ERROR [0001] : No suitable provider for component
> de.softproject.xe.standalone.feature:eclipse.feature was found in
> searchPath de.softproject.xe
> ERROR [0001] : Filter
> (&(target.nl=en)(target.os=win32)(target.ws=win32)(|(tar get.arch=ia64)(target.arch=ia64_32)(target.arch=x86)(target. arch=x86_64)))
> does not match the current property set
>
>
> Not sure what part the last line plays. I think I have a proper match
> for feature de.softproject.xe.standalone.feature in my rmap which looks
> like
>
> ..
> <rm:locator pattern="^de\.softproject\.xe(\..+)?"
> searchPathRef="de.softproject.xe"/>
> ..
> <rm:searchPath name="de.softproject.xe">
> <rm:provider componentTypes="osgi.bundle,eclipse.feature,buckminster"
> readerType="svn"
> mutable="true"
> source="true">
> <rm:uri
> format=" https://{0}:{1}@80.xxx.xxxx.xxx/svn/MAIN/Products/Eclipse-RC P/XSLEasy/trunk/{2}">
>
> <bc:propertyRef key="svn.user"/>
> <bc:propertyRef key="svn.password"/>
> <bc:propertyRef key="buckminster.component"/>
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
>
> I have Target.* set to meaningful values.
>
Re: "No suitable provider" error with svn provider [message #556199 is a reply to message #556063] Tue, 31 August 2010 10:29 Go to previous messageGo to next message
Tomsen  is currently offline Tomsen Friend
Messages: 42
Registered: July 2010
Member
Quote:
Do you have all target.xxx set to '*' ? Even target.nl?


No, I have a buckminster.properties which sets target.arch, target.os and target.ws.

target.os=win32
target.ws=win32
target.arch=x86


I don't set target.nl. Should I?

Is there any way to trace settings Buckminster sees?
Re: "No suitable provider" error with svn provider [message #556223 is a reply to message #556199] Tue, 31 August 2010 11:36 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Thomas,

On 08/31/2010 12:29 PM, Tomsen wrote:
> Quote:
>> Do you have all target.xxx set to '*' ? Even target.nl?
>
>
> No, I have a buckminster.properties which sets target.arch, target.os
> and target.ws.
>
OK, so then the reported error makes sense.

>
> target.os=win32
> target.ws=win32
> target.arch=x86
>
>
> I don't set target.nl. Should I?
>
In this case, yes.

> Is there any way to trace settings Buckminster sees?

Not beyond what it has already reported but the info is in the output
from your original post:

ERROR [0001] : Filter
(&(target.nl=en)(target.os=win32)(target.ws=win32)(|(tar get.arch=ia64)(target.arch=ia64_32)(target.arch=x86)(target. arch=x86_64)))
does not match the current property set

With this line, Buckminster tells you that the component was rejected
because the filter didn't match. The problem in this case is that the
filter requires target.nl=en. Setting target.nl to '*' will make this
filter return true since '*' is a substitute for all possible values.

HTH,
- thomas
Re: "No suitable provider" error with svn provider [message #556388 is a reply to message #556223] Wed, 01 September 2010 07:00 Go to previous messageGo to next message
Tomsen  is currently offline Tomsen Friend
Messages: 42
Registered: July 2010
Member
Thomas,
thx. I added
    <cq:property key="target.nl" value="*"/>


to my developer.cquery and it magically worked ...

I am puzzled now because I simply adapted the developer.cquery from the mailapp tutorial to my needs and this prop isn't contained there.
When I try "Resolve to Wizard" for the developer.cquery in the mailapp case it works without this error ... any ideas why this might be the case?

Anyways thanks again Thomas, I appreciate your work very much. Smile
Re: "No suitable provider" error with svn provider [message #556392 is a reply to message #556388] Wed, 01 September 2010 07:12 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 09/01/2010 09:00 AM, Tomsen wrote:
> Thomas,
> thx. I added
> <cq:property key="target.nl" value="*"/>
>
>
> to my developer.cquery and it magically worked ...
> I am puzzled now because I simply adapted the developer.cquery from the
> mailapp tutorial to my needs and this prop isn't contained there. When I
> try "Resolve to Wizard" for the developer.cquery in the mailapp case it
> works without this error ... any ideas why this might be the case?

The mailapp tutorial will not make an attempt to resolve features that are targeted for specific languages so there's no
need to set the target.nl property. Your app however, requires the 'de.softproject.xe.standalone.feature' and this
feature is obviously only available for specific languages. Hence the need to provide a language of choice (using
target.nl=en) or specify that any comparison against this property should yield true (using target.nl=*)

No magic really, Buckminster is just honoring the rules expressed in the feature.

Regards,
Thomas Hallgren
Re: "No suitable provider" error with svn provider [message #557654 is a reply to message #556392] Wed, 08 September 2010 12:51 Go to previous message
Tomsen  is currently offline Tomsen Friend
Messages: 42
Registered: July 2010
Member
Thomas,
absolutely right, some dev had settings for nl, arch, os and ws in there. That was a bit unexpected. The joy of automizing foreign code ... Fixed this and it works now.

best regards

-Thomas
Previous Topic:authentication cancelled error
Next Topic: "svn: authentication cancelled" error
Goto Forum:
  


Current Time: Fri Mar 29 00:06:32 GMT 2024

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

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

Back to the top