Re: [commons] download releases link broken
On 8/9/07, Julius Davies [EMAIL PROTECTED] wrote: Go here: http://commons.apache.org/ Click on Releases (mirrored) link on the left (underneath Download). Unfortunately it points to: http://jakarta.apache.org/site/downloads/downloads_commons.html Which returns 404. Fixed, thanks. Niall -- yours, Julius Davies - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discuss] Slide + HttpComponents = TLP
While I would like to get rid of HttpClient 3.x rather sooner than later, there's no denyig that it will stay with us for several years to come. From this angle, it would make sense to move the WebDAV client as it is. Maybe that could be the first step. If there is a reasonable interest of developers to help support the 3.x based WebDAV client, I am in favor of cutting it out. I hope that this discussion will heat up a bit next week. (while I'm away...) Leaving the server-side code of Slide in Jakarta will surely give the new project a better start. That code would be a huge burden on my mind, and probably not mine alone. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discuss] Slide + HttpComponents = TLP
2007/8/10, Roland Weber [EMAIL PROTECTED]: Oliver Zeigermann wrote: Martin's and also my hopes had been that when the - indeed useful - WebDAV client was moved to a different project it could actually be revived. Reasons are that it is functional, useful and of much less complexity than the server. I would at least volunteer to support the initial move (including cleanup) to HttpComponents and once it is there am confident it will attract further contributors. The command line client should be dropped, really. So the idea would be to leave the server part behind and just cut out the WebDAV client based on HttpClient 3.x during the move? HttpClient 4.x has no API similarity to 3.x at all, so it is inevitable that the WebDAV client be ported to the new 4.0 API if it's supposed to have a future. Content related parts should be re-usable, but everything on the method level will need to be re-written. Got that. Moving Slide, or the WebDAV client from Slide, is one option. Another option is to leave Slide and it's 3.x based WebDAV client behind and just start with a new WebDAV client based on the 4.0 API in the new project. That would significantly reduce the administrative overhead and does not preclude code re-use from Slide. Maybe that could be a second step. While I would like to get rid of HttpClient 3.x rather sooner than later, there's no denyig that it will stay with us for several years to come. From this angle, it would make sense to move the WebDAV client as it is. Maybe that could be the first step. WDYT? Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discuss] Slide + HttpComponents = TLP
Oliver Zeigermann wrote: Martin's and also my hopes had been that when the - indeed useful - WebDAV client was moved to a different project it could actually be revived. Reasons are that it is functional, useful and of much less complexity than the server. I would at least volunteer to support the initial move (including cleanup) to HttpComponents and once it is there am confident it will attract further contributors. The command line client should be dropped, really. So the idea would be to leave the server part behind and just cut out the WebDAV client based on HttpClient 3.x during the move? HttpClient 4.x has no API similarity to 3.x at all, so it is inevitable that the WebDAV client be ported to the new 4.0 API if it's supposed to have a future. Content related parts should be re-usable, but everything on the method level will need to be re-written. Moving Slide, or the WebDAV client from Slide, is one option. Another option is to leave Slide and it's 3.x based WebDAV client behind and just start with a new WebDAV client based on the 4.0 API in the new project. That would significantly reduce the administrative overhead and does not preclude code re-use from Slide. While I would like to get rid of HttpClient 3.x rather sooner than later, there's no denyig that it will stay with us for several years to come. From this angle, it would make sense to move the WebDAV client as it is. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discuss] Slide + HttpComponents = TLP
2007/8/6, Roland Weber [EMAIL PROTECTED]: Oleg Kalnichevski wrote: Slide seems pretty inactive at the moment. I am just wondering how many developers out there would be willing to contribute on a more or less regular basis to the maintenance and further development of Slide, or the new TLP will effectively end up tasked with the job of trying to recreate the community around the old Slide code base, albeit with a somewhat reduced scope. Indeed a valid concern. This discussion should show how much interest there is in the Slide community. I'm not eager to sift through the backlog of 180 open issues on my own. If the Slide community is inactive, I'd prefer that HttpComponents goes TLP on it's own with a transport scope. Client WebDAV support could be added if and when community interest arises, and we wouldn't have a huge chunk of code with which we're not familiar. I agree that there is little chance to revive the server part of Slide for reasons that should not be discussed here. However, Martin's and also my hopes had been that when the - indeed useful - WebDAV client was moved to a different project it could actually be revived. Reasons are that it is functional, useful and of much less complexity than the server. I would at least volunteer to support the initial move (including cleanup) to HttpComponents and once it is there am confident it will attract further contributors. The command line client should be dropped, really. Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HttpClient 3.x Homepage
Hello Henri, Sorry, yeah. Just doing things at the macro level and then trying to figure out what got screwed up lower down. So what should we do? Since it's too late to keep the page in place, we thought about setting it up somewhere below //jakarta.a.o/httpcomponents/ and redirecting from //commons.a.o/httpclient/ back to Jakarta. Oleg meant to combine that with the 3.1 release, but we could also just move the page for now. I have some time I can spend on it this weekend. cheers, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [discuss] Slide + HttpComponents = TLP
2007/8/10, Roland Weber [EMAIL PROTECTED]: While I would like to get rid of HttpClient 3.x rather sooner than later, there's no denyig that it will stay with us for several years to come. From this angle, it would make sense to move the WebDAV client as it is. Maybe that could be the first step. If there is a reasonable interest of developers to help support the 3.x based WebDAV client, I am in favor of cutting it out. I hope that this discussion will heat up a bit next week. (while I'm away...) Let's see if there is... Leaving the server-side code of Slide in Jakarta will surely give the new project a better start. That code would be a huge burden on my mind, and probably not mine alone. Right. Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
