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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
