Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Unable to resolve buckminster component on svn
Unable to resolve buckminster component on svn [message #378886] Tue, 29 July 2008 14:09 Go to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
Hi there,

I must do something wrong but I can't find what ...

I'd like to materialize a component. This is a Buckminster type component so it possess a buckminster.cspec at the root of the project.
> <?xml version="1.0" encoding="UTF-8"?>
> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0" name="Hd3dServices" componentType="buckminster" version="1.0.0" versionType="OSGi">
> <cs:dependencies>
> <cs:dependency name="Hd3dServicesModel" componentType="buckminster" versionDesignator="[1.0.0,1.0.0]" versionType="OSGi"/>
> <cs:dependency name="antlr" componentType="maven" versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
> <cs:dependency name="asm/asm-attrs" componentType="maven" versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
> <cs:dependency name="cglib" componentType="maven" versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
> <cs:dependency name="com.noelios.restlet" componentType="maven" versionDesignator="[1.1-M4,1.1-M4]" versionType="Triplet"/>
> <cs:dependency name="com.noelios.restlet/com.noelios.restlet.ext.servlet" componentType="maven" versionDesignator="[1.1-M4,1.1-M4]" versionType="Triplet"/>
> <cs:dependency name="dom4j" componentType="maven" versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
> <cs:dependency name="ehcache" componentType="maven" versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
> <cs:dependency name="hibernate" componentType="maven" versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
> <cs:dependency name="hibernate/hibernate-annotations" componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]" versionType="OSGi"/>
> <cs:dependency name="hibernate/hibernate-commons-annotations" componentType="maven" versionDesignator="[3.0.0.ga,3.0.0.ga]" versionType="OSGi"/>
> <cs:dependency name="jta" componentType="maven" versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
> <cs:dependency name="mysql/mysql-connector-java" componentType="maven" versionDesignator="[5.1.6,5.1.6]" versionType="OSGi"/>
> <cs:dependency name="org.hibernate/ejb3-persistence" componentType="maven" versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]" versionType="Triplet"/>
> </cs:dependencies>
> </cs:cspec>


I put this component on svn and wrote an RMAP to materialize it.
This is the RMAP :
> <?xml version="1.0" encoding="UTF-8"?>
> <rmap
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>
> <searchPath name="hd3d_setF">
> <provider readerType="svn" componentTypes="buckminster,eclipse.feature,osgi.bundle" mutable="true" source="true">
> <uri format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
> <bc:propertyRef key="svn.login"/>
> <bc:propertyRef key="svn.passwd"/>
> <bc:propertyRef key="buckminster.component" />
> </uri>
> </provider>
> </searchPath>
>
> <searchPath name="default">
> <!--
> Let's try orbit first and then maven. The componentTypes will discriminate and
> make it quick.
> -->
> <provider readerType="eclipse.import" componentTypes="osgi.bundle" mutable="false" source="false">
> <uri format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
> </provider>
> <provider readerType="maven2" componentTypes="maven" mutable="false" source="false">
> <uri format="http://devwin07/archiva/repository/internal/" />
> </provider>
> <provider readerType="maven2" componentTypes="maven" mutable="false" source="false">
> <uri format="http://www.ibiblio.org/maven2/" />
> </provider>
> <provider readerType="maven" componentTypes="maven" mutable="false" source="false">
> <uri format="http://maven.restlet.org/" />
> </provider>
> </searchPath>
>
> <locator pattern="Hd3dServices" searchPathRef="hd3d_setF" />
> <locator pattern="Hd3dServicesModel" searchPathRef="hd3d_setF" />
> <locator pattern=".*" searchPathRef="default" />
> </rmap>

While resolving the quey I have the following error :
> ERROR [0001] : No suitable provider for component Hd3dServices was found in searchPath hd3d_setF
> ERROR [0001] : Rejecting provider svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}): No component match was found

I tried turning the log level to debug and here is the output:
> Hd3dServices: Using resolver rmap
> Found two entries for component javax.wsdl:osgi.bundle. Version 1.4.0.v200806030407 located at L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version 1.5.1.v200806030408 at L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
> Hd3dServices: Using resource map file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
> Hd3dServices: Using search path hd3d_setF
> Hd3dServices: Trying provider svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
> Hd3dServices: trunk/head will be searched
> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
> blocked(class org.eclipse.core.internal.events.AutoBuildJob[Building workspace])
> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
> Reading remote file svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
> Hd3dServices: Rejecting provider svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}): No component match was found
> Hd3dServices: No provider was found that could resolve the request

The svn reader found the component on SVN but reject it ... Worst, it doesn't read the buckminster.cspec....
The query I used to materialize this component is the following :
> <?xml version="1.0" encoding="UTF-8"?>
> <cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="hd3d.rmap">
> <cq:rootRequest name="Hd3dServices"/>
> <cq:advisorNode namePattern="junit" skipComponent="true"/>
> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core" skipComponent="true"/>
> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
> <cq:advisorNode namePattern="xerces/xercesImpl" skipComponent="true"/>
> </cq:componentQuery>

This query successfully resolves if the Hd3dServices project is in the workspace but fails while trying to access to the SVN repository.
Any ideas ?

Regards,
Guillaume
Re: Unable to resolve buckminster component on svn [message #378891 is a reply to message #378886] Tue, 29 July 2008 20:21 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Guillaume,
I'm not sure what's wrong here. Everything seems to be in order.
Does the project have a .settings/org.eclipse.buckminster.core.prefs
file present (I guess the answer is no, but just to make sure)?

Regards,
Thomas Hallgren

Guillaume CHATELET wrote:
> Hi there,
>
> I must do something wrong but I can't find what ...
>
> I'd like to materialize a component. This is a Buckminster type
> component so it possess a buckminster.cspec at the root of the project.
>> <?xml version="1.0" encoding="UTF-8"?>
>> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
>> name="Hd3dServices" componentType="buckminster" version="1.0.0"
>> versionType="OSGi">
>> <cs:dependencies>
>> <cs:dependency name="Hd3dServicesModel"
>> componentType="buckminster" versionDesignator="[1.0.0,1.0.0]"
>> versionType="OSGi"/>
>> <cs:dependency name="antlr" componentType="maven"
>> versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
>> <cs:dependency name="asm/asm-attrs" componentType="maven"
>> versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
>> <cs:dependency name="cglib" componentType="maven"
>> versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
>> <cs:dependency name="com.noelios.restlet"
>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>> versionType="Triplet"/>
>> <cs:dependency
>> name="com.noelios.restlet/com.noelios.restlet.ext.servlet"
>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>> versionType="Triplet"/>
>> <cs:dependency name="dom4j" componentType="maven"
>> versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
>> <cs:dependency name="ehcache" componentType="maven"
>> versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
>> <cs:dependency name="hibernate" componentType="maven"
>> versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
>> <cs:dependency name="hibernate/hibernate-annotations"
>> componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]"
>> versionType="OSGi"/>
>> <cs:dependency name="hibernate/hibernate-commons-annotations"
>> componentType="maven" versionDesignator="[3.0.0.ga,3.0.0.ga]"
>> versionType="OSGi"/>
>> <cs:dependency name="jta" componentType="maven"
>> versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
>> <cs:dependency name="mysql/mysql-connector-java"
>> componentType="maven" versionDesignator="[5.1.6,5.1.6]"
>> versionType="OSGi"/>
>> <cs:dependency name="org.hibernate/ejb3-persistence"
>> componentType="maven" versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]"
>> versionType="Triplet"/>
>> </cs:dependencies>
>> </cs:cspec>
>
>
> I put this component on svn and wrote an RMAP to materialize it.
> This is the RMAP :
>> <?xml version="1.0" encoding="UTF-8"?>
>> <rmap
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>>
>> <searchPath name="hd3d_setF">
>> <provider readerType="svn"
>> componentTypes="buckminster,eclipse.feature,osgi.bundle"
>> mutable="true" source="true">
>> <uri
>> format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
>>
>> <bc:propertyRef key="svn.login"/>
>> <bc:propertyRef key="svn.passwd"/>
>> <bc:propertyRef key="buckminster.component" />
>> </uri>
>> </provider>
>> </searchPath>
>>
>> <searchPath name="default">
>> <!--
>> Let's try orbit first and then maven. The componentTypes
>> will discriminate and
>> make it quick.
>> -->
>> <provider readerType="eclipse.import"
>> componentTypes="osgi.bundle" mutable="false" source="false">
>> <uri
>> format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
>>
>> </provider>
>> <provider readerType="maven2" componentTypes="maven"
>> mutable="false" source="false">
>> <uri format="http://devwin07/archiva/repository/internal/" />
>> </provider>
>> <provider readerType="maven2" componentTypes="maven"
>> mutable="false" source="false">
>> <uri format="http://www.ibiblio.org/maven2/" />
>> </provider>
>> <provider readerType="maven" componentTypes="maven"
>> mutable="false" source="false">
>> <uri format="http://maven.restlet.org/" />
>> </provider>
>> </searchPath>
>>
>> <locator pattern="Hd3dServices"
>> searchPathRef="hd3d_setF" />
>> <locator pattern="Hd3dServicesModel" searchPathRef="hd3d_setF" />
>> <locator pattern=".*" searchPathRef="default" />
>> </rmap>
>
> While resolving the quey I have the following error :
>> ERROR [0001] : No suitable provider for component Hd3dServices was
>> found in searchPath hd3d_setF
>> ERROR [0001] : Rejecting provider
>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>> No component match was found
>
> I tried turning the log level to debug and here is the output:
>> Hd3dServices: Using resolver rmap
>> Found two entries for component javax.wsdl:osgi.bundle. Version
>> 1.4.0.v200806030407 located at
>> L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version
>> 1.5.1.v200806030408 at
>> L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
>> Hd3dServices: Using resource map
>> file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
>> Hd3dServices: Using search path hd3d_setF
>> Hd3dServices: Trying provider
>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
>> Hd3dServices: trunk/head will be searched
>> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
>> blocked(class org.eclipse.core.internal.events.AutoBuildJob[Building
>> workspace])
>> Listing remote folder
>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
>> Reading remote file
>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
>>
>> Hd3dServices: Rejecting provider
>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>> No component match was found
>> Hd3dServices: No provider was found that could resolve the request
>
> The svn reader found the component on SVN but reject it ... Worst, it
> doesn't read the buckminster.cspec....
> The query I used to materialize this component is the following :
>> <?xml version="1.0" encoding="UTF-8"?>
>> <cq:componentQuery
>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>> resourceMap="hd3d.rmap">
>> <cq:rootRequest name="Hd3dServices"/>
>> <cq:advisorNode namePattern="junit" skipComponent="true"/>
>> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core"
>> skipComponent="true"/>
>> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
>> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
>> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
>> <cq:advisorNode namePattern="xerces/xercesImpl"
>> skipComponent="true"/>
>> </cq:componentQuery>
>
> This query successfully resolves if the Hd3dServices project is in the
> workspace but fails while trying to access to the SVN repository.
> Any ideas ?
>
> Regards,
> Guillaume
Re: Unable to resolve buckminster component on svn [message #378897 is a reply to message #378891] Wed, 30 July 2008 08:11 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
Right the answer is no and this seems to stop the resolution process.

Guillaume

Thomas Hallgren wrote:
> Hi Guillaume,
> I'm not sure what's wrong here. Everything seems to be in order.
> Does the project have a .settings/org.eclipse.buckminster.core.prefs
> file present (I guess the answer is no, but just to make sure)?
>
> Regards,
> Thomas Hallgren
>
> Guillaume CHATELET wrote:
>> Hi there,
>>
>> I must do something wrong but I can't find what ...
>>
>> I'd like to materialize a component. This is a Buckminster type
>> component so it possess a buckminster.cspec at the root of the project.
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
>>> name="Hd3dServices" componentType="buckminster" version="1.0.0"
>>> versionType="OSGi">
>>> <cs:dependencies>
>>> <cs:dependency name="Hd3dServicesModel"
>>> componentType="buckminster" versionDesignator="[1.0.0,1.0.0]"
>>> versionType="OSGi"/>
>>> <cs:dependency name="antlr" componentType="maven"
>>> versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
>>> <cs:dependency name="asm/asm-attrs" componentType="maven"
>>> versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
>>> <cs:dependency name="cglib" componentType="maven"
>>> versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
>>> <cs:dependency name="com.noelios.restlet"
>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>> versionType="Triplet"/>
>>> <cs:dependency
>>> name="com.noelios.restlet/com.noelios.restlet.ext.servlet"
>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>> versionType="Triplet"/>
>>> <cs:dependency name="dom4j" componentType="maven"
>>> versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
>>> <cs:dependency name="ehcache" componentType="maven"
>>> versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
>>> <cs:dependency name="hibernate" componentType="maven"
>>> versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
>>> <cs:dependency name="hibernate/hibernate-annotations"
>>> componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]"
>>> versionType="OSGi"/>
>>> <cs:dependency name="hibernate/hibernate-commons-annotations"
>>> componentType="maven" versionDesignator="[3.0.0.ga,3.0.0.ga]"
>>> versionType="OSGi"/>
>>> <cs:dependency name="jta" componentType="maven"
>>> versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
>>> <cs:dependency name="mysql/mysql-connector-java"
>>> componentType="maven" versionDesignator="[5.1.6,5.1.6]"
>>> versionType="OSGi"/>
>>> <cs:dependency name="org.hibernate/ejb3-persistence"
>>> componentType="maven" versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]"
>>> versionType="Triplet"/>
>>> </cs:dependencies>
>>> </cs:cspec>
>>
>>
>> I put this component on svn and wrote an RMAP to materialize it.
>> This is the RMAP :
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <rmap
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
>>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
>>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>>> <searchPath name="hd3d_setF">
>>> <provider readerType="svn"
>>> componentTypes="buckminster,eclipse.feature,osgi.bundle"
>>> mutable="true" source="true">
>>> <uri
>>> format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
>>>
>>> <bc:propertyRef key="svn.login"/>
>>> <bc:propertyRef key="svn.passwd"/>
>>> <bc:propertyRef key="buckminster.component" />
>>> </uri>
>>> </provider>
>>> </searchPath>
>>> <searchPath name="default">
>>> <!--
>>> Let's try orbit first and then maven. The componentTypes
>>> will discriminate and
>>> make it quick.
>>> -->
>>> <provider readerType="eclipse.import"
>>> componentTypes="osgi.bundle" mutable="false" source="false">
>>> <uri
>>> format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
>>>
>>> </provider>
>>> <provider readerType="maven2" componentTypes="maven"
>>> mutable="false" source="false">
>>> <uri
>>> format="http://devwin07/archiva/repository/internal/" />
>>> </provider>
>>> <provider readerType="maven2" componentTypes="maven"
>>> mutable="false" source="false">
>>> <uri format="http://www.ibiblio.org/maven2/" />
>>> </provider>
>>> <provider readerType="maven" componentTypes="maven"
>>> mutable="false" source="false">
>>> <uri format="http://maven.restlet.org/" />
>>> </provider>
>>> </searchPath>
>>> <locator pattern="Hd3dServices"
>>> searchPathRef="hd3d_setF" />
>>> <locator pattern="Hd3dServicesModel" searchPathRef="hd3d_setF" />
>>> <locator pattern=".*" searchPathRef="default" />
>>> </rmap>
>>
>> While resolving the quey I have the following error :
>>> ERROR [0001] : No suitable provider for component Hd3dServices was
>>> found in searchPath hd3d_setF
>>> ERROR [0001] : Rejecting provider
>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>> No component match was found
>>
>> I tried turning the log level to debug and here is the output:
>>> Hd3dServices: Using resolver rmap
>>> Found two entries for component javax.wsdl:osgi.bundle. Version
>>> 1.4.0.v200806030407 located at
>>> L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version
>>> 1.5.1.v200806030408 at
>>> L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
>>> Hd3dServices: Using resource map
>>> file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
>>> Hd3dServices: Using search path hd3d_setF
>>> Hd3dServices: Trying provider
>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
>>> Hd3dServices: trunk/head will be searched
>>> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
>>> blocked(class org.eclipse.core.internal.events.AutoBuildJob[Building
>>> workspace])
>>> Listing remote folder
>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
>>> Reading remote file
>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
>>>
>>> Hd3dServices: Rejecting provider
>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>> No component match was found
>>> Hd3dServices: No provider was found that could resolve the request
>>
>> The svn reader found the component on SVN but reject it ... Worst, it
>> doesn't read the buckminster.cspec....
>> The query I used to materialize this component is the following :
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <cq:componentQuery
>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>> resourceMap="hd3d.rmap">
>>> <cq:rootRequest name="Hd3dServices"/>
>>> <cq:advisorNode namePattern="junit" skipComponent="true"/>
>>> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core"
>>> skipComponent="true"/>
>>> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
>>> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
>>> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
>>> <cq:advisorNode namePattern="xerces/xercesImpl"
>>> skipComponent="true"/>
>>> </cq:componentQuery>
>>
>> This query successfully resolves if the Hd3dServices project is in the
>> workspace but fails while trying to access to the SVN repository.
>> Any ideas ?
>>
>> Regards,
>> Guillaume
Re: Unable to resolve buckminster component on svn [message #378974 is a reply to message #378897] Mon, 04 August 2008 14:21 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
Thomas,

Have you got any clue of why Buckminster needs this file .settings/org.eclipse.buckminster.core.prefs and how I can add it ?

Regards,
Guillaume

Guillaume CHATELET wrote:
> Right the answer is no and this seems to stop the resolution process.
>
> Guillaume
>
> Thomas Hallgren wrote:
>> Hi Guillaume,
>> I'm not sure what's wrong here. Everything seems to be in order.
>> Does the project have a .settings/org.eclipse.buckminster.core.prefs
>> file present (I guess the answer is no, but just to make sure)?
>>
>> Regards,
>> Thomas Hallgren
>>
>> Guillaume CHATELET wrote:
>>> Hi there,
>>>
>>> I must do something wrong but I can't find what ...
>>>
>>> I'd like to materialize a component. This is a Buckminster type
>>> component so it possess a buckminster.cspec at the root of the project.
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
>>>> name="Hd3dServices" componentType="buckminster" version="1.0.0"
>>>> versionType="OSGi">
>>>> <cs:dependencies>
>>>> <cs:dependency name="Hd3dServicesModel"
>>>> componentType="buckminster" versionDesignator="[1.0.0,1.0.0]"
>>>> versionType="OSGi"/>
>>>> <cs:dependency name="antlr" componentType="maven"
>>>> versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
>>>> <cs:dependency name="asm/asm-attrs" componentType="maven"
>>>> versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
>>>> <cs:dependency name="cglib" componentType="maven"
>>>> versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
>>>> <cs:dependency name="com.noelios.restlet"
>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>> versionType="Triplet"/>
>>>> <cs:dependency
>>>> name="com.noelios.restlet/com.noelios.restlet.ext.servlet"
>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>> versionType="Triplet"/>
>>>> <cs:dependency name="dom4j" componentType="maven"
>>>> versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
>>>> <cs:dependency name="ehcache" componentType="maven"
>>>> versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
>>>> <cs:dependency name="hibernate" componentType="maven"
>>>> versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
>>>> <cs:dependency name="hibernate/hibernate-annotations"
>>>> componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]"
>>>> versionType="OSGi"/>
>>>> <cs:dependency
>>>> name="hibernate/hibernate-commons-annotations" componentType="maven"
>>>> versionDesignator="[3.0.0.ga,3.0.0.ga]" versionType="OSGi"/>
>>>> <cs:dependency name="jta" componentType="maven"
>>>> versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
>>>> <cs:dependency name="mysql/mysql-connector-java"
>>>> componentType="maven" versionDesignator="[5.1.6,5.1.6]"
>>>> versionType="OSGi"/>
>>>> <cs:dependency name="org.hibernate/ejb3-persistence"
>>>> componentType="maven" versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]"
>>>> versionType="Triplet"/>
>>>> </cs:dependencies>
>>>> </cs:cspec>
>>>
>>>
>>> I put this component on svn and wrote an RMAP to materialize it.
>>> This is the RMAP :
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <rmap
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
>>>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
>>>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>>> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>>>> <searchPath name="hd3d_setF">
>>>> <provider readerType="svn"
>>>> componentTypes="buckminster,eclipse.feature,osgi.bundle"
>>>> mutable="true" source="true">
>>>> <uri
>>>> format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
>>>>
>>>> <bc:propertyRef key="svn.login"/>
>>>> <bc:propertyRef key="svn.passwd"/>
>>>> <bc:propertyRef key="buckminster.component" />
>>>> </uri>
>>>> </provider>
>>>> </searchPath>
>>>> <searchPath name="default">
>>>> <!--
>>>> Let's try orbit first and then maven. The componentTypes
>>>> will discriminate and
>>>> make it quick.
>>>> -->
>>>> <provider readerType="eclipse.import"
>>>> componentTypes="osgi.bundle" mutable="false" source="false">
>>>> <uri
>>>> format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
>>>>
>>>> </provider>
>>>> <provider readerType="maven2" componentTypes="maven"
>>>> mutable="false" source="false">
>>>> <uri
>>>> format="http://devwin07/archiva/repository/internal/" />
>>>> </provider>
>>>> <provider readerType="maven2" componentTypes="maven"
>>>> mutable="false" source="false">
>>>> <uri format="http://www.ibiblio.org/maven2/" />
>>>> </provider>
>>>> <provider readerType="maven" componentTypes="maven"
>>>> mutable="false" source="false">
>>>> <uri format="http://maven.restlet.org/" />
>>>> </provider>
>>>> </searchPath>
>>>> <locator pattern="Hd3dServices"
>>>> searchPathRef="hd3d_setF" />
>>>> <locator pattern="Hd3dServicesModel"
>>>> searchPathRef="hd3d_setF" />
>>>> <locator pattern=".*" searchPathRef="default" />
>>>> </rmap>
>>>
>>> While resolving the quey I have the following error :
>>>> ERROR [0001] : No suitable provider for component Hd3dServices was
>>>> found in searchPath hd3d_setF
>>>> ERROR [0001] : Rejecting provider
>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>> No component match was found
>>>
>>> I tried turning the log level to debug and here is the output:
>>>> Hd3dServices: Using resolver rmap
>>>> Found two entries for component javax.wsdl:osgi.bundle. Version
>>>> 1.4.0.v200806030407 located at
>>>> L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version
>>>> 1.5.1.v200806030408 at
>>>> L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
>>>> Hd3dServices: Using resource map
>>>> file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
>>>> Hd3dServices: Using search path hd3d_setF
>>>> Hd3dServices: Trying provider
>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
>>>> Hd3dServices: trunk/head will be searched
>>>> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
>>>> blocked(class org.eclipse.core.internal.events.AutoBuildJob[Building
>>>> workspace])
>>>> Listing remote folder
>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
>>>> Reading remote file
>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
>>>>
>>>> Hd3dServices: Rejecting provider
>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>> No component match was found
>>>> Hd3dServices: No provider was found that could resolve the request
>>>
>>> The svn reader found the component on SVN but reject it ... Worst, it
>>> doesn't read the buckminster.cspec....
>>> The query I used to materialize this component is the following :
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <cq:componentQuery
>>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>>> resourceMap="hd3d.rmap">
>>>> <cq:rootRequest name="Hd3dServices"/>
>>>> <cq:advisorNode namePattern="junit" skipComponent="true"/>
>>>> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core"
>>>> skipComponent="true"/>
>>>> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
>>>> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
>>>> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
>>>> <cq:advisorNode namePattern="xerces/xercesImpl"
>>>> skipComponent="true"/>
>>>> </cq:componentQuery>
>>>
>>> This query successfully resolves if the Hd3dServices project is in
>>> the workspace but fails while trying to access to the SVN repository.
>>> Any ideas ?
>>>
>>> Regards,
>>> Guillaume
Re: Unable to resolve buckminster component on svn [message #378975 is a reply to message #378974] Mon, 04 August 2008 14:53 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Guillaume,
Buckminster doesn't need that file. It does however check for its
existence since it may contain properties that relocates the
cspec/cspex. The attempt to access that file is normal and not the cause
of your error.

- thomas


Guillaume CHATELET wrote:
> Thomas,
>
> Have you got any clue of why Buckminster needs this file
> .settings/org.eclipse.buckminster.core.prefs and how I can add it ?
>
> Regards,
> Guillaume
>
> Guillaume CHATELET wrote:
>> Right the answer is no and this seems to stop the resolution process.
>>
>> Guillaume
>>
>> Thomas Hallgren wrote:
>>> Hi Guillaume,
>>> I'm not sure what's wrong here. Everything seems to be in order.
>>> Does the project have a .settings/org.eclipse.buckminster.core.prefs
>>> file present (I guess the answer is no, but just to make sure)?
>>>
>>> Regards,
>>> Thomas Hallgren
>>>
>>> Guillaume CHATELET wrote:
>>>> Hi there,
>>>>
>>>> I must do something wrong but I can't find what ...
>>>>
>>>> I'd like to materialize a component. This is a Buckminster type
>>>> component so it possess a buckminster.cspec at the root of the project.
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
>>>>> name="Hd3dServices" componentType="buckminster" version="1.0.0"
>>>>> versionType="OSGi">
>>>>> <cs:dependencies>
>>>>> <cs:dependency name="Hd3dServicesModel"
>>>>> componentType="buckminster" versionDesignator="[1.0.0,1.0.0]"
>>>>> versionType="OSGi"/>
>>>>> <cs:dependency name="antlr" componentType="maven"
>>>>> versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
>>>>> <cs:dependency name="asm/asm-attrs" componentType="maven"
>>>>> versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
>>>>> <cs:dependency name="cglib" componentType="maven"
>>>>> versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
>>>>> <cs:dependency name="com.noelios.restlet"
>>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>>> versionType="Triplet"/>
>>>>> <cs:dependency
>>>>> name="com.noelios.restlet/com.noelios.restlet.ext.servlet"
>>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>>> versionType="Triplet"/>
>>>>> <cs:dependency name="dom4j" componentType="maven"
>>>>> versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
>>>>> <cs:dependency name="ehcache" componentType="maven"
>>>>> versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
>>>>> <cs:dependency name="hibernate" componentType="maven"
>>>>> versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
>>>>> <cs:dependency name="hibernate/hibernate-annotations"
>>>>> componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]"
>>>>> versionType="OSGi"/>
>>>>> <cs:dependency
>>>>> name="hibernate/hibernate-commons-annotations"
>>>>> componentType="maven" versionDesignator="[3.0.0.ga,3.0.0.ga]"
>>>>> versionType="OSGi"/>
>>>>> <cs:dependency name="jta" componentType="maven"
>>>>> versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
>>>>> <cs:dependency name="mysql/mysql-connector-java"
>>>>> componentType="maven" versionDesignator="[5.1.6,5.1.6]"
>>>>> versionType="OSGi"/>
>>>>> <cs:dependency name="org.hibernate/ejb3-persistence"
>>>>> componentType="maven" versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]"
>>>>> versionType="Triplet"/>
>>>>> </cs:dependencies>
>>>>> </cs:cspec>
>>>>
>>>>
>>>> I put this component on svn and wrote an RMAP to materialize it.
>>>> This is the RMAP :
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <rmap
>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
>>>>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
>>>>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>>>> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>>>>> <searchPath name="hd3d_setF">
>>>>> <provider readerType="svn"
>>>>> componentTypes="buckminster,eclipse.feature,osgi.bundle"
>>>>> mutable="true" source="true">
>>>>> <uri
>>>>> format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
>>>>>
>>>>> <bc:propertyRef key="svn.login"/>
>>>>> <bc:propertyRef key="svn.passwd"/>
>>>>> <bc:propertyRef key="buckminster.component" />
>>>>> </uri>
>>>>> </provider>
>>>>> </searchPath>
>>>>> <searchPath name="default">
>>>>> <!--
>>>>> Let's try orbit first and then maven. The
>>>>> componentTypes will discriminate and
>>>>> make it quick.
>>>>> -->
>>>>> <provider readerType="eclipse.import"
>>>>> componentTypes="osgi.bundle" mutable="false" source="false">
>>>>> <uri
>>>>> format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
>>>>>
>>>>> </provider>
>>>>> <provider readerType="maven2" componentTypes="maven"
>>>>> mutable="false" source="false">
>>>>> <uri
>>>>> format="http://devwin07/archiva/repository/internal/" />
>>>>> </provider>
>>>>> <provider readerType="maven2" componentTypes="maven"
>>>>> mutable="false" source="false">
>>>>> <uri format="http://www.ibiblio.org/maven2/" />
>>>>> </provider>
>>>>> <provider readerType="maven" componentTypes="maven"
>>>>> mutable="false" source="false">
>>>>> <uri format="http://maven.restlet.org/" />
>>>>> </provider>
>>>>> </searchPath>
>>>>> <locator pattern="Hd3dServices"
>>>>> searchPathRef="hd3d_setF" />
>>>>> <locator pattern="Hd3dServicesModel"
>>>>> searchPathRef="hd3d_setF" />
>>>>> <locator pattern=".*"
>>>>> searchPathRef="default" />
>>>>> </rmap>
>>>>
>>>> While resolving the quey I have the following error :
>>>>> ERROR [0001] : No suitable provider for component Hd3dServices
>>>>> was found in searchPath hd3d_setF
>>>>> ERROR [0001] : Rejecting provider
>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>>> No component match was found
>>>>
>>>> I tried turning the log level to debug and here is the output:
>>>>> Hd3dServices: Using resolver rmap
>>>>> Found two entries for component javax.wsdl:osgi.bundle. Version
>>>>> 1.4.0.v200806030407 located at
>>>>> L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version
>>>>> 1.5.1.v200806030408 at
>>>>> L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
>>>>> Hd3dServices: Using resource map
>>>>> file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
>>>>> Hd3dServices: Using search path hd3d_setF
>>>>> Hd3dServices: Trying provider
>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
>>>>> Hd3dServices: trunk/head will be searched
>>>>> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
>>>>> blocked(class
>>>>> org.eclipse.core.internal.events.AutoBuildJob[Building workspace])
>>>>> Listing remote folder
>>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
>>>>> Reading remote file
>>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
>>>>>
>>>>> Hd3dServices: Rejecting provider
>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>>> No component match was found
>>>>> Hd3dServices: No provider was found that could resolve the request
>>>>
>>>> The svn reader found the component on SVN but reject it ... Worst,
>>>> it doesn't read the buckminster.cspec....
>>>> The query I used to materialize this component is the following :
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>> <cq:componentQuery
>>>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>>>> resourceMap="hd3d.rmap">
>>>>> <cq:rootRequest name="Hd3dServices"/>
>>>>> <cq:advisorNode namePattern="junit" skipComponent="true"/>
>>>>> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core"
>>>>> skipComponent="true"/>
>>>>> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
>>>>> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
>>>>> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
>>>>> <cq:advisorNode namePattern="xerces/xercesImpl"
>>>>> skipComponent="true"/>
>>>>> </cq:componentQuery>
>>>>
>>>> This query successfully resolves if the Hd3dServices project is in
>>>> the workspace but fails while trying to access to the SVN repository.
>>>> Any ideas ?
>>>>
>>>> Regards,
>>>> Guillaume
Re: Unable to resolve buckminster component on svn [message #378976 is a reply to message #378975] Mon, 04 August 2008 15:10 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
Hi Thomas,

Maybe it's the Subclipse plugin that generates the error but as soon as I commited an empty .settings/org.eclipse.buckminster.core.prefs file to the SVN server I was able to materialize the components.
This is quite strange.

The SVN server is used with the svn protocol, not the http one (ie: svn://svn.hd3d.fr/hd3d/trunk and not http://svn.hd3d.fr/hd3d/trunk ) it surely has nothing to do with it but it's the only thing that differs from my other svn server and I did never had this pb with the other server...

Does it ring a bell ?

Guillaume

Thomas Hallgren wrote:
> Hi Guillaume,
> Buckminster doesn't need that file. It does however check for its
> existence since it may contain properties that relocates the
> cspec/cspex. The attempt to access that file is normal and not the cause
> of your error.
>
> - thomas
>
>
> Guillaume CHATELET wrote:
>> Thomas,
>>
>> Have you got any clue of why Buckminster needs this file
>> .settings/org.eclipse.buckminster.core.prefs and how I can add it ?
>>
>> Regards,
>> Guillaume
>>
>> Guillaume CHATELET wrote:
>>> Right the answer is no and this seems to stop the resolution process.
>>>
>>> Guillaume
>>>
>>> Thomas Hallgren wrote:
>>>> Hi Guillaume,
>>>> I'm not sure what's wrong here. Everything seems to be in order.
>>>> Does the project have a .settings/org.eclipse.buckminster.core.prefs
>>>> file present (I guess the answer is no, but just to make sure)?
>>>>
>>>> Regards,
>>>> Thomas Hallgren
>>>>
>>>> Guillaume CHATELET wrote:
>>>>> Hi there,
>>>>>
>>>>> I must do something wrong but I can't find what ...
>>>>>
>>>>> I'd like to materialize a component. This is a Buckminster type
>>>>> component so it possess a buckminster.cspec at the root of the
>>>>> project.
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <cs:cspec xmlns:cs="http://www.eclipse.org/buckminster/CSpec-1.0"
>>>>>> name="Hd3dServices" componentType="buckminster" version="1.0.0"
>>>>>> versionType="OSGi">
>>>>>> <cs:dependencies>
>>>>>> <cs:dependency name="Hd3dServicesModel"
>>>>>> componentType="buckminster" versionDesignator="[1.0.0,1.0.0]"
>>>>>> versionType="OSGi"/>
>>>>>> <cs:dependency name="antlr" componentType="maven"
>>>>>> versionDesignator="[2.7.6,2.7.6]" versionType="OSGi"/>
>>>>>> <cs:dependency name="asm/asm-attrs" componentType="maven"
>>>>>> versionDesignator="[1.5.3,1.5.3]" versionType="OSGi"/>
>>>>>> <cs:dependency name="cglib" componentType="maven"
>>>>>> versionDesignator="[2.1_3,2.1_3]" versionType="Triplet"/>
>>>>>> <cs:dependency name="com.noelios.restlet"
>>>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>>>> versionType="Triplet"/>
>>>>>> <cs:dependency
>>>>>> name="com.noelios.restlet/com.noelios.restlet.ext.servlet"
>>>>>> componentType="maven" versionDesignator="[1.1-M4,1.1-M4]"
>>>>>> versionType="Triplet"/>
>>>>>> <cs:dependency name="dom4j" componentType="maven"
>>>>>> versionDesignator="[1.6.1,1.6.1]" versionType="OSGi"/>
>>>>>> <cs:dependency name="ehcache" componentType="maven"
>>>>>> versionDesignator="[1.2.3,1.2.3]" versionType="OSGi"/>
>>>>>> <cs:dependency name="hibernate" componentType="maven"
>>>>>> versionDesignator="[3.2.6.ga,3.2.6.ga]" versionType="OSGi"/>
>>>>>> <cs:dependency name="hibernate/hibernate-annotations"
>>>>>> componentType="maven" versionDesignator="[3.3.1.ga,3.3.1.ga]"
>>>>>> versionType="OSGi"/>
>>>>>> <cs:dependency
>>>>>> name="hibernate/hibernate-commons-annotations"
>>>>>> componentType="maven" versionDesignator="[3.0.0.ga,3.0.0.ga]"
>>>>>> versionType="OSGi"/>
>>>>>> <cs:dependency name="jta" componentType="maven"
>>>>>> versionDesignator="[1.1.0,1.1.0]" versionType="OSGi"/>
>>>>>> <cs:dependency name="mysql/mysql-connector-java"
>>>>>> componentType="maven" versionDesignator="[5.1.6,5.1.6]"
>>>>>> versionType="OSGi"/>
>>>>>> <cs:dependency name="org.hibernate/ejb3-persistence"
>>>>>> componentType="maven"
>>>>>> versionDesignator="[3.3.2.Beta1,3.3.2.Beta1]" versionType="Triplet"/>
>>>>>> </cs:dependencies>
>>>>>> </cs:cspec>
>>>>>
>>>>>
>>>>> I put this component on svn and wrote an RMAP to materialize it.
>>>>> This is the RMAP :
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <rmap
>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>>> xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
>>>>>> xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
>>>>>> xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
>>>>>> xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
>>>>>> <searchPath name="hd3d_setF">
>>>>>> <provider readerType="svn"
>>>>>> componentTypes="buckminster,eclipse.feature,osgi.bundle"
>>>>>> mutable="true" source="true">
>>>>>> <uri
>>>>>> format=" http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}">
>>>>>>
>>>>>> <bc:propertyRef key="svn.login"/>
>>>>>> <bc:propertyRef key="svn.passwd"/>
>>>>>> <bc:propertyRef key="buckminster.component" />
>>>>>> </uri>
>>>>>> </provider>
>>>>>> </searchPath>
>>>>>> <searchPath name="default">
>>>>>> <!--
>>>>>> Let's try orbit first and then maven. The
>>>>>> componentTypes will discriminate and
>>>>>> make it quick.
>>>>>> -->
>>>>>> <provider readerType="eclipse.import"
>>>>>> componentTypes="osgi.bundle" mutable="false" source="false">
>>>>>> <uri
>>>>>> format=" http://download.eclipse.org/tools/orbit/downloads/drops/R200 80611105805/orbitBundles-R20080611105805.map"/>
>>>>>>
>>>>>> </provider>
>>>>>> <provider readerType="maven2" componentTypes="maven"
>>>>>> mutable="false" source="false">
>>>>>> <uri
>>>>>> format="http://devwin07/archiva/repository/internal/" />
>>>>>> </provider>
>>>>>> <provider readerType="maven2" componentTypes="maven"
>>>>>> mutable="false" source="false">
>>>>>> <uri format="http://www.ibiblio.org/maven2/" />
>>>>>> </provider>
>>>>>> <provider readerType="maven" componentTypes="maven"
>>>>>> mutable="false" source="false">
>>>>>> <uri format="http://maven.restlet.org/" />
>>>>>> </provider>
>>>>>> </searchPath>
>>>>>> <locator pattern="Hd3dServices"
>>>>>> searchPathRef="hd3d_setF" />
>>>>>> <locator pattern="Hd3dServicesModel"
>>>>>> searchPathRef="hd3d_setF" />
>>>>>> <locator pattern=".*"
>>>>>> searchPathRef="default" />
>>>>>> </rmap>
>>>>>
>>>>> While resolving the quey I have the following error :
>>>>>> ERROR [0001] : No suitable provider for component Hd3dServices
>>>>>> was found in searchPath hd3d_setF
>>>>>> ERROR [0001] : Rejecting provider
>>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>>>> No component match was found
>>>>>
>>>>> I tried turning the log level to debug and here is the output:
>>>>>> Hd3dServices: Using resolver rmap
>>>>>> Found two entries for component javax.wsdl:osgi.bundle. Version
>>>>>> 1.4.0.v200806030407 located at
>>>>>> L:/eclipse/plugins/javax.wsdl_1.4.0.v200806030407.jar and version
>>>>>> 1.5.1.v200806030408 at
>>>>>> L:/eclipse/plugins/javax.wsdl_1.5.1.v200806030408.jar
>>>>>> Hd3dServices: Using resource map
>>>>>> file:/T:/travail/src/Hd3dWorkspace/Queries/hd3d.rmap
>>>>>> Hd3dServices: Using search path hd3d_setF
>>>>>> Hd3dServices: Trying provider
>>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2})
>>>>>>
>>>>>> Hd3dServices: trunk/head will be searched
>>>>>> Listing remote folder svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF#HEAD
>>>>>> blocked(class
>>>>>> org.eclipse.core.internal.events.AutoBuildJob[Building workspace])
>>>>>> Listing remote folder
>>>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices#HEAD
>>>>>>
>>>>>> Reading remote file
>>>>>> svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubator.Hd3dSer vices/.settings/org.eclipse.buckminster.core.prefs#HEAD
>>>>>>
>>>>>> Hd3dServices: Rejecting provider
>>>>>> svn( http://{0}:{1}@svn.hd3d.fr/hd3d/trunk/hd3d/app/setF/incubato r.{2}):
>>>>>> No component match was found
>>>>>> Hd3dServices: No provider was found that could resolve the request
>>>>>
>>>>> The svn reader found the component on SVN but reject it ... Worst,
>>>>> it doesn't read the buckminster.cspec....
>>>>> The query I used to materialize this component is the following :
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <cq:componentQuery
>>>>>> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
>>>>>> resourceMap="hd3d.rmap">
>>>>>> <cq:rootRequest name="Hd3dServices"/>
>>>>>> <cq:advisorNode namePattern="junit" skipComponent="true"/>
>>>>>> <cq:advisorNode namePattern="aspectwerkz/aspectwerkz-core"
>>>>>> skipComponent="true"/>
>>>>>> <cq:advisorNode namePattern="stax/stax-ri" skipComponent="true"/>
>>>>>> <cq:advisorNode namePattern="xalan" skipComponent="true"/>
>>>>>> <cq:advisorNode namePattern="xml-apis" skipComponent="true"/>
>>>>>> <cq:advisorNode namePattern="xerces/xercesImpl"
>>>>>> skipComponent="true"/>
>>>>>> </cq:componentQuery>
>>>>>
>>>>> This query successfully resolves if the Hd3dServices project is in
>>>>> the workspace but fails while trying to access to the SVN repository.
>>>>> Any ideas ?
>>>>>
>>>>> Regards,
>>>>> Guillaume
Re: Unable to resolve buckminster component on svn [message #378977 is a reply to message #378976] Mon, 04 August 2008 15:30 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Guillaume CHATELET wrote:
> Hi Thomas,
>
> Maybe it's the Subclipse plugin that generates the error but as soon as
> I commited an empty .settings/org.eclipse.buckminster.core.prefs file to
> the SVN server I was able to materialize the components.
> This is quite strange.
>
> The SVN server is used with the svn protocol, not the http one (ie:
> svn://svn.hd3d.fr/hd3d/trunk and not http://svn.hd3d.fr/hd3d/trunk ) it
> surely has nothing to do with it but it's the only thing that differs
> from my other svn server and I did never had this pb with the other
> server...
>
> Does it ring a bell ?
>
Hmm, maybe. There is some code in place to detect if an exception means
that a file is non-existent or if the error is of another nature. The
code throws a FileNotFoundException for the former and Buckminster deals
with that gracefully. If that code fails (because the exception is
different using certain protocols), then it might cause the resolution
to terminate.

Do you have a chance to debug this? The place that I think would be most
relevant is the catch clause on line 287 in the
org.eclipse.buckminster.subclipse.internal.SvnRemoteFileRead er class.

- thomas
Re: Unable to resolve buckminster component on svn [message #378978 is a reply to message #378977] Mon, 04 August 2008 16:33 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
You were right Thomas, the following exception is raised :
> org.tigris.subversion.javahl.clientexception: two versioned resources are unrelated
> svn: unable to find repository location for ' svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setf/incubator.hd3dser vices/.settings/org.eclipse.buckminster.core.prefs' in revision 773

Buckminster tries to find the strings "file not found" or "path not found" in the exception message but as you can see, it's not the case thus throwing an IOException instead of the FileNotFoundException you expected.

You can patch the code at line 301 by adding a test against the string "unable to find repository location".
if(lcMsg.contains("file not found") || lcMsg.contains("path not found") || lcMsg.contains("unable to find repository location"))

Here is the patch that does the trick :

### Eclipse Workspace Patch 1.0
#P org.eclipse.buckminster.subclipse
Index: src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
============================================================ =======
--- src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java (revision 9497)
+++ src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java (working copy)
@@ -298,7 +298,7 @@
else
{
String lcMsg = msg.toLowerCase();
- if(lcMsg.contains("file not found") || lcMsg.contains("path not found"))
+ if(lcMsg.contains("file not found") || lcMsg.contains("path not found") || lcMsg.contains("unable to find repository location"))
{
if(logger.isDebugEnabled())
logger.debug(String.format("Remote file not found %s", key));


Cheers,
Guillaume

Thomas Hallgren wrote:
> Hmm, maybe. There is some code in place to detect if an exception means
> that a file is non-existent or if the error is of another nature. The
> code throws a FileNotFoundException for the former and Buckminster deals
> with that gracefully. If that code fails (because the exception is
> different using certain protocols), then it might cause the resolution
> to terminate.
>
> Do you have a chance to debug this? The place that I think would be most
> relevant is the catch clause on line 287 in the
> org.eclipse.buckminster.subclipse.internal.SvnRemoteFileRead er class.
>
> - thomas
Re: Unable to resolve buckminster component on svn [message #378979 is a reply to message #378978] Mon, 04 August 2008 16:37 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume ChateletFriend
Messages: 146
Registered: July 2009
Senior Member
Hmm, the same patch should be applied to the Subversive plugin also
org.eclipse.buckminster.subversive.internal.SubversiveRemote FileReader : l.243

Guillaume CHATELET wrote:
> You were right Thomas, the following exception is raised :
>> org.tigris.subversion.javahl.clientexception: two versioned resources
>> are unrelated
>> svn: unable to find repository location for
>> ' svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setf/incubator.hd3dser vices/.settings/org.eclipse.buckminster.core.prefs'
>> in revision 773
>
> Buckminster tries to find the strings "file not found" or "path not
> found" in the exception message but as you can see, it's not the case
> thus throwing an IOException instead of the FileNotFoundException you
> expected.
>
> You can patch the code at line 301 by adding a test against the string
> "unable to find repository location".
> if(lcMsg.contains("file not found") || lcMsg.contains("path not found")
> || lcMsg.contains("unable to find repository location"))
>
> Here is the patch that does the trick :
>
> ### Eclipse Workspace Patch 1.0
> #P org.eclipse.buckminster.subclipse
> Index:
> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
>
> ============================================================ =======
> ---
> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
> (revision 9497)
> +++
> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
> (working copy)
> @@ -298,7 +298,7 @@
> else
> {
> String lcMsg = msg.toLowerCase();
> - if(lcMsg.contains("file not found") ||
> lcMsg.contains("path not found"))
> + if(lcMsg.contains("file not found") ||
> lcMsg.contains("path not found") || lcMsg.contains("unable to find
> repository location"))
> {
> if(logger.isDebugEnabled())
> logger.debug(String.format("Remote file not
> found %s", key));
>
>
> Cheers,
> Guillaume
>
> Thomas Hallgren wrote:
>> Hmm, maybe. There is some code in place to detect if an exception
>> means that a file is non-existent or if the error is of another
>> nature. The code throws a FileNotFoundException for the former and
>> Buckminster deals with that gracefully. If that code fails (because
>> the exception is different using certain protocols), then it might
>> cause the resolution to terminate.
>>
>> Do you have a chance to debug this? The place that I think would be
>> most relevant is the catch clause on line 287 in the
>> org.eclipse.buckminster.subclipse.internal.SvnRemoteFileRead er class.
>>
>> - thomas
Re: Unable to resolve buckminster component on svn [message #378980 is a reply to message #378979] Mon, 04 August 2008 17:03 Go to previous message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
Hi Guillaume,
Patch applied (to both) in revision 9508.

Thanks for the effort.

- thomas

Guillaume CHATELET wrote:
> Hmm, the same patch should be applied to the Subversive plugin also
> org.eclipse.buckminster.subversive.internal.SubversiveRemote FileReader :
> l.243
>
> Guillaume CHATELET wrote:
>> You were right Thomas, the following exception is raised :
>>> org.tigris.subversion.javahl.clientexception: two versioned resources
>>> are unrelated
>>> svn: unable to find repository location for
>>> ' svn://svn.hd3d.fr/hd3d/trunk/hd3d/app/setf/incubator.hd3dser vices/.settings/org.eclipse.buckminster.core.prefs'
>>> in revision 773
>>
>> Buckminster tries to find the strings "file not found" or "path not
>> found" in the exception message but as you can see, it's not the case
>> thus throwing an IOException instead of the FileNotFoundException you
>> expected.
>>
>> You can patch the code at line 301 by adding a test against the string
>> "unable to find repository location".
>> if(lcMsg.contains("file not found") || lcMsg.contains("path not
>> found") || lcMsg.contains("unable to find repository location"))
>>
>> Here is the patch that does the trick :
>>
>> ### Eclipse Workspace Patch 1.0
>> #P org.eclipse.buckminster.subclipse
>> Index:
>> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
>>
>> ============================================================ =======
>> ---
>> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
>> (revision 9497)
>> +++
>> src/java/org/eclipse/buckminster/subclipse/internal/SvnRemot eFileReader.java
>> (working copy)
>> @@ -298,7 +298,7 @@
>> else
>> {
>> String lcMsg = msg.toLowerCase();
>> - if(lcMsg.contains("file not found") ||
>> lcMsg.contains("path not found"))
>> + if(lcMsg.contains("file not found") ||
>> lcMsg.contains("path not found") || lcMsg.contains("unable to find
>> repository location"))
>> {
>> if(logger.isDebugEnabled())
>> logger.debug(String.format("Remote file not
>> found %s", key));
>>
>>
>> Cheers,
>> Guillaume
>>
>> Thomas Hallgren wrote:
>>> Hmm, maybe. There is some code in place to detect if an exception
>>> means that a file is non-existent or if the error is of another
>>> nature. The code throws a FileNotFoundException for the former and
>>> Buckminster deals with that gracefully. If that code fails (because
>>> the exception is different using certain protocols), then it might
>>> cause the resolution to terminate.
>>>
>>> Do you have a chance to debug this? The place that I think would be
>>> most relevant is the catch clause on line 287 in the
>>> org.eclipse.buckminster.subclipse.internal.SvnRemoteFileRead er class.
>>>
>>> - thomas
Previous Topic:Error materializing to a workspace
Next Topic:URIMatcher explicitly sets IComponentType.UNKNOWN
Goto Forum:
  


Current Time: Thu Apr 25 14:23:46 GMT 2024

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

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

Back to the top