Mark, > What your guys timeframe for migrating up to Jakarta? I think this will > dictate how invloved we get with the branching in your cvs tree.
We have not even started debating on this issue. I personally would VERY STRONGLY favour releasing 3.0 out of Commons first and only then gradually migrating to the Jakarta level as HttpClient undergoes a long complete redesign. Being realistic, 3.0 development should take 8 to 12 months, possibly more. We definitely want to have some presence at the Jakarta level pretty much immediately. Most of the links, though, would still point at the Commons HttpClient resources > I can't come up with one beyond hardcoding Windows EOL's. I seldom use > notepad and always reassign the "txt" extension over to Wordpad on > Windows boxes. Though, this doesn't solve this problem really. All it takes is a simple Ant script. The trouble is I have no idea how to make Maven execute an Ant target as a part of release process. This is where I'd greatly appreciate a bit of help Oleg -----Original Message----- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 16:53 To: Kalnichevski, Oleg Cc: Commons HttpClient Project Subject: Re: Broken link on website Kalnichevski, Oleg wrote: >Mark, >There is a few little problems generating HttpClient 2.0 site using maven rc2: >(1) Currently we generate HttpClient site off the 2.0 branch rather CVS HEAD. The >same changes made to the project.xml in CVS HEAD need to be made in the 2.0 branch. >I'll take care of that unless someone beats me to it > >http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/project.xml?r1=1.43&r2=1.44&diff_format=h > > > What your guys timeframe for migrating up to Jakarta? I think this will dictate how invloved we get with the branching in your cvs tree. >(2) New while background renders HttpClient logo unreadable (white on white). Is >there anything that can be done about it? > > > Again, with migration to Jakrta, you might want to generate some new Logo's >(3) The link to the Commons Logging site in the HttpClient redirect guide still needs >to be fixed. I'll take care of that (again, unless someone beats me to it) > >Otherwise +1 from me > >Oleg > > I went to regenerate the site using rc2 and failed, I generated and put inplace the new mavenized site. the link should work in this location. >PS: > >None of the HttpClient regulars seems proficient enough with maven to be able to >tackle the following request: > >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26499 > >Any pointers as to how this problem can fixed? > > > I can't come up with one beyond hardcoding Windows EOL's. I seldom use notepad and always reassign the "txt" extension over to Wordpad on Windows boxes. Though, this doesn't solve this problem really. >-----Original Message----- >From: Mark R. Diggory [mailto:[EMAIL PROTECTED] >Sent: Monday, April 19, 2004 17:08 >To: Commons HttpClient Project >Subject: Re: Broken link on website > > >Roland Weber wrote: > > > >>Hi guys, >> >>I just found a broken link in the Logging Guide. >>The Commons Logging home page has moved from >> >>http://jakarta.apache.org/commons/logging.html >> >>to >>http://jakarta.apache.org/commons/logging/ >> >>cheers, >> Roland >> >> >> >> >> >I think I'm just going to go ahead and move into place the genreated >maven site like we voted on, I got everrun at work last week. The links >from the maven generated site point to the correct location. > >-Mark > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >*************************************************************************************************** >The information in this email is confidential and may be legally privileged. Access >to this email by anyone other than the intended addressee is unauthorized. If you >are not the intended recipient of this message, any review, disclosure, copying, >distribution, retention, or any action taken or omitted to be taken in reliance on it >is prohibited and may be unlawful. If you are not the intended recipient, please >reply to or forward a copy of this message to the sender and delete the message, any >attachments, and any copies thereof from your system. >*************************************************************************************************** > > *************************************************************************************************** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *************************************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
