On Jan 14, 2008 6:22 AM, sebb <[EMAIL PROTECTED]> wrote:
> On 14/01/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Selon Siegfried Goeschl <[EMAIL PROTECTED]>:
> >
> > > Hi Luc,
> > >
> > > look at
> > >
> > > +)
> > >
> > http://commons.apache.org/sandbox/exec/xref/org/apache/commons/exec/
Forgot to add my own vote
> ->
>
> [ X ] +1 I support this release
> [ ] +0 I am OK with this release
> [ ] -0 OK, but
> [ ] -1 I do not support this release
>
Phil
-
On Jan 14, 2008 2:13 PM, Oliver Heger <[EMAIL PROTECTED]> wrote:
> The artifacts look good, the build also succeeded in all variants (on a
> JDK 1.6). So I am +1 for this release.
>
> Two minor points:
> - On my first attempt to build with maven 2 I got the test failure
> below. However this was no
Stephen Kestle writes:
> [EMAIL PROTECTED] wrote:
> > What about Collections?
> I'll try to find to do at least a patch a week, eh?
Cool! I'll try and keep you busy :)
Richard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 1/12/08, Phil Steitz <[EMAIL PROTECTED]> wrote:
> This is a vote to release commons pool 1.4.
>
> [X] +1 I support this release
> [ ] +0 I am OK with this release
> [ ] -0 OK, but
> [ ] -1 I do not support this release
-Rahul
-
[EMAIL PROTECTED] wrote:
What about Collections?
Yeah - at the moment Stephen Colebourne and I are the only comitters.
He's busy working on a JSR and some other stuff, and I've had some
medical setbacks in the family that mean young children have been handed
around somewhat. It's looking
On Jan 14, 2008 9:13 PM, Oliver Heger <[EMAIL PROTECTED]> wrote:
> The artifacts look good, the build also succeeded in all variants (on a
> JDK 1.6). So I am +1 for this release.
>
> Two minor points:
> - On my first attempt to build with maven 2 I got the test failure
> below. However this was no
+1
Niall Pemberton wrote:
Hi,
Seems like discussion has concluded so trying again...
The changes since the the last release of version 6 in summary:
Changes to the pom.xml:
- Configure NOTICE.txt and LICENSE.txt resources
- add *hack* to put NOTICE/LICENSE in the -javadoc.jar
- Change the
The artifacts look good, the build also succeeded in all variants (on a
JDK 1.6). So I am +1 for this release.
Two minor points:
- On my first attempt to build with maven 2 I got the test failure
below. However this was not reproducable, further builds succeeded. Has
anybody else seen this?
It would be nice if the site said that Java 1.4.2 is required for [pool].
Thank you,
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 14/01/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Jan 14, 2008 2:30 PM, sebb <[EMAIL PROTECTED]> wrote:
> > On 13/01/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > > Commons IO 1.4 release candidate 1 (RC1) is available for review. The
> > > artifacts are here:
> > > http://peopl
On Jan 14, 2008 2:30 PM, sebb <[EMAIL PROTECTED]> wrote:
> On 13/01/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > Commons IO 1.4 release candidate 1 (RC1) is available for review. The
> > artifacts are here:
> > http://people.apache.org/~niallp/io-1.4-RC1/
> >
>
> Just found out that SHA-1 d
On 13/01/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> Commons IO 1.4 release candidate 1 (RC1) is available for review. The
> artifacts are here:
> http://people.apache.org/~niallp/io-1.4-RC1/
>
Just found out that SHA-1 digest files must be called .sha, not .sha1.
See
http://www.apache.org
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
On 14/01/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Selon Siegfried Goeschl <[EMAIL PROTECTED]>:
>
> > Hi Luc,
> >
> > look at
> >
> > +)
> >
> http://commons.apache.org/sandbox/exec/xref/org/apache/commons/exec/StreamPumper.html#77
>
> Couldn't this class be replaced by java.io.PipedInpu
Selon Siegfried Goeschl <[EMAIL PROTECTED]>:
> Hi Luc,
>
> look at
>
> +)
>
http://commons.apache.org/sandbox/exec/xref/org/apache/commons/exec/StreamPumper.html#77
Couldn't this class be replaced by java.io.PipedInputStream and
java.io.PipedOutputStream ?
>
http://commons.apache.org/sandbox/exe
Hi Luc,
look at
+)
http://commons.apache.org/sandbox/exec/xref/org/apache/commons/exec/StreamPumper.html#77
+)
http://commons.apache.org/sandbox/exec/xref/org/apache/commons/exec/DefaultExecutor.html#255
There a lot of ugly code during closing of the various Input/OutputStreams
+) it is dif
On 14/01/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Siegfried Goeschl <[EMAIL PROTECTED]> wrote:
>
>
> > On the downside the current implementation silently drops so many
> > exceptions that I feel a bit uncomfortable about it (or to state it more
> > clearly I would reject such a code du
Siegfried Goeschl <[EMAIL PROTECTED]> wrote:
> On the downside the current implementation silently drops so many
> exceptions that I feel a bit uncomfortable about it (or to state it more
> clearly I would reject such a code during code review) - so I have no
> final conclusion what to do
I'm a
I'm just reading the documentation ... :-)
Cheers,
Siegfried Goeschl
Thorbjørn Ravn Andersen wrote:
Siegfried Goeschl skrev den 10-01-2008 13:41:
I changed the code to use stdout/stderr per default to make
commons-logging an optional dependency but the question remains -
should we support
Hi folks,
fortunately my personal opinion is shared with parts of the commons
community (well, I'm doing some cherry picking here) so I propose
+) remove any logging support forcing an additional dependency
+) provide documentation how to hook in an arbitrary logging API
On the downside the c
21 matches
Mail list logo
