On 11/20/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Nov 18, 2007 6:56 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > On 11/18/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > On Nov 17, 2007 9:39 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > > >
> > > > A while ago, you pointed o
On 11/19/07, sebb <[EMAIL PROTECTED]> wrote:
> On 19/11/2007, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > My preference is we stick with "Commons Foo" rather than "Apache
> > Commons Foo" which is more of a mouthfull. Specifically for the
> > manifest since we have "Vendor" entries which sa
Phil Steitz wrote:
On Sep 3, 2007 8:33 AM, Phil Steitz <[EMAIL PROTECTED]> wrote:
On 9/2/07, Luc Maisonobe <[EMAIL PROTECTED]> wrote:
On 2007-05-15, Phil Steitz wrote:
I agree. So, probably best is to deprecate the current abstract
factories and move to single concrete factories with impl se
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
...and we have a winner!
The vote has passed with the following votes:
+1 (binding): Torsten Curdt, Oliver Heger, Sebastian Bazley, Jörg
Schaible, Dennis Lundberg
+1 (non-binding at the time of his vote, but binding now): Ben Speakmon
+1 (non-binding): Nicolas de Loof,
I'm proceeding with t
+1
Dennis Lundberg wrote:
Hi
This is the fourth attempt to release commons-logging 1.1.1.
Changes since the last go:
- The manifests now has the correct X-Compile-Target-JDK in them
- The manifests no longer mention Jakarta
- [LOGGING-118] Generate source and binary archives.
Release Notes:
h
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects 1
Patch Attached.
On Nov 26, 2007 8:19 PM, Nikunj Trivedi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I have created a Patch having two methods and test cases for both, as
> explained below. Any Comments ?
>
> 1) New Method: ByteArrayOutputStream.toInputStream
> ByteArrayOutputStream exposes its byte
Hi All,
I have created a Patch having two methods and test cases for both, as
explained below. Any Comments ?
1) New Method: ByteArrayOutputStream.toInputStream
ByteArrayOutputStream exposes its byte buffers by toByteArray(), which
creates a fresh buffer and copy existing data to it.
A new method
