That does sound like a great idea to me. The facade could remain as "Jakarta Commons HttpClient" within a commons-httpclient.jar and the functional code as "Jakarta HttpClient" in a httpclient-jar. commons-httclient.jar would then of course depend on httpclient.jar.
There is still quite a bit to discuss on the HttpClient list on how to make the transition, so these are just early ideas.
-jsd
Daniel L. Rall wrote:
Jeff Dever wrote:
...
3) Will you be changing package name?
I'd suggest that the naming conventions of HttpClient be consistant with other top level projects. So the new root package be org.apache.httpclient, website be http://jakarta.apache.org/httpclient/, etc... This would cause some import annoyance and broken links, but consistancy is important. We should take reasonable measures to minimize the disrutpion to users caused by this move.
Jeff, how about providing a set of transitional org.apache.commons.httpclient facades or extension classes for a one release deprecation period? These classes would ship along side the real org.apache.httpclient structure, and all be marked as deprecated, allowing consumers of HTTP Client some warning and a brief period for transition at little cost to the development community.
- Dan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
