Re: Adding a Wagon to the Wagon project

On 20/03/2008, at 6:17 AM, delbd wrote:

> Hello dear wagon developpers,
>
>
> I am facing a situation where i need to deploy my maven2 project to  
> a sourceforge repository. To automate this, i planned to convert the  
> maven1 sourceforge deploy plugin to a wagon provider, so i could use  
> a sf:.... url scheme for the deploy location. Now, i have a few  
> questions for team

Cool :)

It's been a while since I've used sourceforge, but how is this  
different from the ssh wagons?

> 1) (most important), how do i tell Wagon to associate my class  
> (x.y.SourceforgeWagon) to a sf: prefix? It seems the trick is a  
> component.xml file in jar, but i don't find how it got generated  
> during build process

it's the role-hint in components.xml. Add this to your class javadoc:

   @plexus.component role="org.apache.maven.wagon.Wagon"  role-
hint="sf"    instantiation-strategy="per-lookup"

and make sure you use the plexus-maven-plugin to generate  
components.xml (which you can see in the existing providers).

>
>
> 2) Is there any doc on how to build your own Wagon implementation?

No - but we welcome contributions as you explore.

>
>
> 3) is a mvn:install + add that artifact to another project enough to  
> be able to test plugin with my own project?

yes, but you must add the artifact using the <extension> tag (you'll  
see a lot of examples around for webdav).

>
>
> 4) Supposing i make that plugin and it works properly, what are the  
> rules i must follow if i want to propose it to community?

Keep discussing it here, and eventually submit it to JIRA. Make sure  
the code is licensed under the Apache License. You may have to submit  
a license agreement too - but we'll help you out at that point if  
necessary.

Cheers,
Brett

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


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