Michael Becke wrote:
In particular I would like to hear from all the regular committers,
contributors, and users. How do you think this move would effect
HttpClient's visibility, community, and organization?
I see HttpClient as a Jakarta level project. As Oleg has already stated,
its design
Eric,
These are good questions, and I think they summarize well the current
discussion.
Should HttpClient be promoted to a Jakarta project?
- Yes, that would seem to make sense, given the separate mailing list,
the list of other commons libraries it depends upon, the separate
mailing list,
: Re: Promote HttpClient out of commons?
As for supporting multiple platforms, isn't Ant a TLP and is
only
written in Java? HttpClient is already cross-platform because
it's
written in Java -- I don't think there's a requirement that it
be
re-implemented in a different language for each
Kalnichevski, Oleg wrote:
This also affects package naming (org.apache.commons.httpclient vs org.apache.httpclient) which in its turn affects binary compatibility with the previous releases.
Wow cool. Release now under Commons and rename packages later. This
gives us the unique opportunity to
I am a HttpClient user and a Lucene committer.
I don't see any problems in HttpClient moving out of Commons.
However, before you waste time doing that, talk to people
involved in moving projects from Jakarta and making them Top
Level Projects (TLP). Ant, Log4j, etc. have made this move, so
you
Otis, et al
There are several things that in my view make HttpClient not yet ready
for a full-blown TLP status:
* Please correct me if I am wrong, but I always thought that TLPs were
supposed to support multiple platforms, hence their top level status.
Whereas I can certainly imagine HttpClient
* I can hardly think of any subproject within HttpClient project.
Ability to host sub-project within a project is one of the primary
criteria for promoting a project to the top level. I do not think we
qualify
Just as one possible subproject, I have been mulling over in my head
building a
Hey all,
I'm new to the HttpClient mailing list, but here's a couple of newbie
observations:
* Please correct me if I am wrong, but I always thought that TLPs were
supposed to support multiple platforms, hence their top level status.
Whereas I can certainly imagine HttpClient implemented in
Another downside of top-level-hood is the overhead. Jakarta already has
a fully functional PMC and a Charter, as well as an established brand.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net/
otisg wrote:
I am a HttpClient user and a Lucene committer.
I don't see any problems in
Hello folks,
after taking a look on the project list at
http://jakarta.apache.org/, I'd feel comfortable
to see the HTTP Client among them. It sure
wouldn't hurt it's visibility either.
I see two major points why it should not be
promoted to top level status. The technical
reason is the pendig
Hello All,
There has been some discussion lately of promoting HttpClient out of
commons, making it a regular Jakarta project. Before any such move is
made we would need to come to a consensus, and vote, within the
HttpClient community. At this point I would like to encourage everyone
to put
11 matches
Mail list logo
