On 6/24/07, Roland Weber <[EMAIL PROTECTED]> wrote:
1. Keep the httpclient site with the rest of commons and move it to the new TLP domain. We'll have to update the httpclient build with the new location and redeploy. (Anything I've forgotten?) 2. Move the httpclient site to httpcomponents. Since httpcomponents is unlikely to remain in Jakarta indefinitely, that means the site would move again later this year. Two moves within a few months is a bit too disruptive to users for my liking. 3. Keep the httpclient site at it's current location in Jakarta when the rest of the commons site moves. Move it only once to httpcomponents when those leave Jakarta. Please share your thoughts on this. My preferred option is 3, but I don't know how much trouble that will cause when setting up redirects to the new commons site.
Probably some. Plus the svn move will be painful. Either 1 or 2 seem fine to me and whatever those committing to HttpComponent/HttpClient want to do is fine by me. 3 seems painful to do. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
