proposal, a wagon for sourceforge repositories

[david delbecq-6]

Hello,

please find attached a proposed wagon to connect to sourceforge repository.

The repository urls of this wagon have the form:

sf://sourceforge.net/project[/package[/release]]

It's able, in such repositories, to upload file (authenticated, using
sourceforge releases system) and download them (unauthenticated). As
sourceforge is not multilevel in folder deepness (to the opposite of a
filesystem), behind the scene it will map the "repository + filepath" to
a simple package/release/file format. The final names will depend on
repository configuration (see above), but will remain consistent and
invisible to wagon user.

It is also able to download sourceforge files, even if they were not
uploaded using wagon.


Work is based in maven1 sourceforge plugin. Licence is yet to be decided.

Any comments / suggestion / flaming are welcomed from list users :)

Note: it's based on old wagon api, because we need it to be working with
existing maven2 installations.

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

[Jason van Zyl-2]

Why would you use anything other then the proliferation of options  
with normal HTTP.

Why don't you get them to use something more standard so that you can  
use what everyone else is using.

On 13-Apr-08, at 8:44 AM, david delbecq wrote:

> Hello,
>
> please find attached a proposed wagon to connect to sourceforge  
> repository.
>
> The repository urls of this wagon have the form:
>
> sf://sourceforge.net/project[/package[/release]]
>
> It's able, in such repositories, to upload file (authenticated,  
> using sourceforge releases system) and download them  
> (unauthenticated). As sourceforge is not multilevel in folder  
> deepness (to the opposite of a filesystem), behind the scene it will  
> map the "repository + filepath" to a simple package/release/file  
> format. The final names will depend on repository configuration (see  
> above), but will remain consistent and invisible to wagon user.
>
> It is also able to download sourceforge files, even if they were not  
> uploaded using wagon.
>
>
> Work is based in maven1 sourceforge plugin. Licence is yet to be  
> decided.
>
> Any comments / suggestion / flaming are welcomed from list users :)
>
> Note: it's based on old wagon api, because we need it to be working  
> with existing maven2 installations.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-dev-unsubscribe@...
> For additional commands, e-mail: wagon-dev-help@...
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

Three people can keep a secret provided two of them are dead.

-- Unknown




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

[david delbecq-6]

Jason van Zyl a écrit :
> Why would you use anything other then the proliferation of options
> with normal HTTP.
>
> Why don't you get them to use something more standard so that you can
> use what everyone else is using.

Because, for sourceforge hosted projects

1) you don't have the allowance to host the binaries (jars of others)
inside the sourceforge web hosting area. So the idea of having a maven
repo inside your project.sf.net/ is no go
2) To get artifact hosted on maven2 official repo, you need to either
have your own repo (which is impossible on sourceforge) or ask for
manual installation of package (4 weeks delay!)
3) The process of releasing one or several file for sourceforge implies:
Uploading to an anonymous ftp server, login to your project, eventually
create package and release, select amongst the list of files currently
in the ftp server which one concerns you, select various informations
about that file and then confirm you want to release it. Considering my
experience, it takes about 30 minutes per file to do manually. In the
past (maven1) i have found the maven release plugin very useful for this
and it's the primary aim of this wagon. This wagon is able to also
download, but it's not it's primary objective.


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

[Jason van Zyl-2]

On 13-Apr-08, at 11:49 AM, david delbecq wrote:

>
> Jason van Zyl a écrit :
>> Why would you use anything other then the proliferation of options  
>> with normal HTTP.
>>
>> Why don't you get them to use something more standard so that you  
>> can use what everyone else is using.
>
> Because, for sourceforge hosted projects
>
> 1) you don't have the allowance to host the binaries (jars of  
> others) inside the sourceforge web hosting area. So the idea of  
> having a maven repo inside your project.sf.net/ is no go

Fine, let's create one for you at Contegix that you guys can use.

>
> 2) To get artifact hosted on maven2 official repo, you need to  
> either have your own repo (which is impossible on sourceforge) or  
> ask for manual installation of package (4 weeks delay!)

Lots of sourceforge projects have direct syncs with the maven2  
repository. They get synced every 4 hours.

>
> 3) The process of releasing one or several file for sourceforge  
> implies: Uploading to an anonymous ftp server, login to your  
> project, eventually create package and release, select amongst the  
> list of files currently in the ftp server which one concerns you,  
> select various informations about that file and then confirm you  
> want to release it. Considering my experience, it takes about 30  
> minutes per file to do manually. In the past (maven1) i have found  
> the maven release plugin very useful for this and it's the primary  
> aim of this wagon. This wagon is able to also download, but it's not  
> it's primary objective.

Then just avoid and we can do 1) or 2) for you guys.

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

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

-- Eric Hoffer, Reflections on the Human Condition




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

[brettporter]

I didn't see this attached. If it can reuse as much of the existing  
wagon implementations as possible, I can see some value in this to  
make releases easier - though maybe a separate plugin hooked into the  
release process makes more sense?

- Brett

On 13/04/2008, at 11:44 PM, david delbecq wrote:

> Hello,
>
> please find attached a proposed wagon to connect to sourceforge  
> repository.
>
> The repository urls of this wagon have the form:
>
> sf://sourceforge.net/project[/package[/release]]
>
> It's able, in such repositories, to upload file (authenticated,  
> using sourceforge releases system) and download them  
> (unauthenticated). As sourceforge is not multilevel in folder  
> deepness (to the opposite of a filesystem), behind the scene it will  
> map the "repository + filepath" to a simple package/release/file  
> format. The final names will depend on repository configuration (see  
> above), but will remain consistent and invisible to wagon user.
>
> It is also able to download sourceforge files, even if they were not  
> uploaded using wagon.
>
>
> Work is based in maven1 sourceforge plugin. Licence is yet to be  
> decided.
>
> Any comments / suggestion / flaming are welcomed from list users :)
>
> Note: it's based on old wagon api, because we need it to be working  
> with existing maven2 installations.
>
> ---------------------------------------------------------------------
> 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@...