registering Wagon with 1.0-beta2

View: New views
3 Messages — Rating Filter:   Alert me  

registering Wagon with 1.0-beta2

by david delbecq-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I have trouble getting my custom wagon protocol to be registered to
wagon provider. I am using 1.0-beta-2 api because that's the one
embedded in maven 2, and i aim to get it used by a maven project.

I created a class that extends AbstractWagon, and i create
src/main/ressources/META-INF/plexus/components.xml that has the
following content

<component-set>
  <components>
    <component>
      <role>org.apache.maven.wagon.Wagon</role>
      <role-hint>sf</role-hint>
     
<implementation>org.apache.maven.wagon.providers.SfWagon</implementation>
      <instantiation-strategy>per-lookup</instantiation-strategy>
    </component>
  </components>
</component-set>

I also added a static block in class with a "System.out.println" and a
"Thread.dumpStack()" to get hint on classloading

My static block proves that plexus is loading my class during
exploration, so i suppose it takes properly into account my components.xml
However, when it comes tu using the wagon, i get this:

[WARNING] repository metadata for: 'snapshot
net.sf:sfDeployementTest:0.0.1-SNAPSHOT' could not be retrieved from
repository: testSf due to an error: Unsupported Protocol: 'sf': Cannot
find wagon which supports the requested protocol: sf
[INFO] Repository 'testSf' will be blacklisted


I know that rc-1-SNAPSHOT does all that registering automaticaly, but i
need to work with 1.0-beta-2 provider api

Running mvn deploy with -X argument give no usefull information either :/

Help welcomed, this block my tests :)

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-dev-unsubscribe@...
For additional commands, e-mail: wagon-dev-help@...


Re: registering Wagon with 1.0-beta2

by brettporter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

You have the <extension> for your provider declared in the build?

What version of Maven?

On 01/04/2008, at 6:03 AM, delbd wrote:

> Hello,
>
> I have trouble getting my custom wagon protocol to be registered to  
> wagon provider. I am using 1.0-beta-2 api because that's the one  
> embedded in maven 2, and i aim to get it used by a maven project.
>
> I created a class that extends AbstractWagon, and i create src/main/
> ressources/META-INF/plexus/components.xml that has the following  
> content
>
> <component-set>
> <components>
>   <component>
>     <role>org.apache.maven.wagon.Wagon</role>
>     <role-hint>sf</role-hint>
>     <implementation>org.apache.maven.wagon.providers.SfWagon</
> implementation>
>     <instantiation-strategy>per-lookup</instantiation-strategy>
>   </component>
> </components>
> </component-set>
>
> I also added a static block in class with a "System.out.println" and  
> a "Thread.dumpStack()" to get hint on classloading
>
> My static block proves that plexus is loading my class during  
> exploration, so i suppose it takes properly into account my  
> components.xml
> However, when it comes tu using the wagon, i get this:
>
> [WARNING] repository metadata for: 'snapshot  
> net.sf:sfDeployementTest:0.0.1-SNAPSHOT' could not be retrieved from  
> repository: testSf due to an error: Unsupported Protocol: 'sf':  
> Cannot find wagon which supports the requested protocol: sf
> [INFO] Repository 'testSf' will be blacklisted
>
>
> I know that rc-1-SNAPSHOT does all that registering automaticaly,  
> but i need to work with 1.0-beta-2 provider api
>
> Running mvn deploy with -X argument give no usefull information  
> either :/
>
> Help welcomed, this block my tests :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-dev-unsubscribe@...
> For additional commands, e-mail: wagon-dev-help@...
>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-dev-unsubscribe@...
For additional commands, e-mail: wagon-dev-help@...


Re: registering Wagon with 1.0-beta2

by david delbecq-6 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ok, got it, it was a classpath issue. One of my dependencies was
bringing along an old version of xerces, as a result, constructor was
failing because of a silented "NoSuchMethodError" in one of my wagon
properties initialisation :)

Sorry for bothering ;)
Delbecq David

Brett Porter a écrit :

> You have the <extension> for your provider declared in the build?
>
> What version of Maven?
>
> On 01/04/2008, at 6:03 AM, delbd wrote:
>
>> Hello,
>>
>> I have trouble getting my custom wagon protocol to be registered to
>> wagon provider. I am using 1.0-beta-2 api because that's the one
>> embedded in maven 2, and i aim to get it used by a maven project.
>>
>> I created a class that extends AbstractWagon, and i create
>> src/main/ressources/META-INF/plexus/components.xml that has the
>> following content
>>
>> <component-set>
>> <components>
>>   <component>
>>     <role>org.apache.maven.wagon.Wagon</role>
>>     <role-hint>sf</role-hint>
>>    
>> <implementation>org.apache.maven.wagon.providers.SfWagon</implementation>
>>
>>     <instantiation-strategy>per-lookup</instantiation-strategy>
>>   </component>
>> </components>
>> </component-set>
>>
>> I also added a static block in class with a "System.out.println" and
>> a "Thread.dumpStack()" to get hint on classloading
>>
>> My static block proves that plexus is loading my class during
>> exploration, so i suppose it takes properly into account my
>> components.xml
>> However, when it comes tu using the wagon, i get this:
>>
>> [WARNING] repository metadata for: 'snapshot
>> net.sf:sfDeployementTest:0.0.1-SNAPSHOT' could not be retrieved from
>> repository: testSf due to an error: Unsupported Protocol: 'sf':
>> Cannot find wagon which supports the requested protocol: sf
>> [INFO] Repository 'testSf' will be blacklisted
>>
>>
>> I know that rc-1-SNAPSHOT does all that registering automaticaly, but
>> i need to work with 1.0-beta-2 provider api
>>
>> Running mvn deploy with -X argument give no usefull information
>> either :/
>>
>> Help welcomed, this block my tests :)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-dev-unsubscribe@...
>> For additional commands, e-mail: wagon-dev-help@...
>>
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-dev-unsubscribe@...
> For additional commands, e-mail: wagon-dev-help@...


---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-dev-unsubscribe@...
For additional commands, e-mail: wagon-dev-help@...