Martin van den Bemt wrote: > +1 to keep httpclient and move it to httpcomponents.
I've taken a first look at things. Moving the tree in Subversion should be painless. Then we have to update the SVN links on the website. Changing them in xdocs is easy, but it will take some careful review to make sure that the site generated from the new tree location is still OK. I haven't stumbled across relative links to outside resources yet, so maybe we're not going to run into problems from that side. The commons list of subprojects is hard-coded, so the missing httpclient subtree in SVN should not affect it. We will have a problem when the commons website moves though. I see several options: 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. I don't have a Maven 1 environment set up to play around right now, but I'll give it a try next week-end if time permits. Oleg will be busy with the upcoming releases. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
