You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Joerg Hohwiller <jo...@j-hohwiller.de> on 2006/05/08 20:30:24 UTC
Re: [PROPOSAL] Move Commons Proxy to Proper
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
James Carman wrote:
> Outside projects (currently my Syringe project and the "Crispy" project
> at sourceforge) are beginning to want to use Commons Proxy, but are finding
> it difficult since it's in the sandbox and no releases are available. I
> believe Proxy's API is close to being ready for a release candidate.
> Moving it to the proper will help us prepare it for an
> official release. There are some classes that I might remove altogether,
> since they feel rather "frameworky" (the CachedProvider is one of them).
> I've cut/signed a mock 1.0 release and it can be found in my home directory
> (/home/jcarman/commons-proxy-1.0-release) on www.apache.org. Can you folks
> take a look at it and let me know what you think?
A little late on this but anyways...
Just to meantion that the framework of my open-source project at sourceforge
is also looking at commons-proxy. I would apreciate if proxy would move to
proper. It looks quite stable and ready to use for me...
>
>
Take care
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEX45AmPuec2Dcv/8RAiXkAKCFcFEUAKe2O5jZiTI1YdITvP6SNACfTheA
HP7Q+ul3+tLS1vMAMvudIFs=
=h4//
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [PROPOSAL] Move Commons Proxy to Proper
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Mon, 2006-05-08 at 20:30 +0200, Joerg Hohwiller wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
>
> James Carman wrote:
> > Outside projects (currently my Syringe project and the "Crispy" project
> > at sourceforge) are beginning to want to use Commons Proxy, but are finding
> > it difficult since it's in the sandbox and no releases are available. I
> > believe Proxy's API is close to being ready for a release candidate.
> > Moving it to the proper will help us prepare it for an
> > official release. There are some classes that I might remove altogether,
> > since they feel rather "frameworky" (the CachedProvider is one of them).
> > I've cut/signed a mock 1.0 release and it can be found in my home directory
> > (/home/jcarman/commons-proxy-1.0-release) on www.apache.org. Can you folks
> > take a look at it and let me know what you think?
> A little late on this but anyways...
> Just to meantion that the framework of my open-source project at sourceforge
> is also looking at commons-proxy. I would apreciate if proxy would move to
> proper. It looks quite stable and ready to use for me...
i'm generally in favour
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org