On Jan 6, 2008 2:33 AM, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, January 05, 2008 5:52 PM
> > To: Commons Developers List
> > Subject: [IO] Planning IO 1.4 release
> >
> > I would like to get an IO
On Jan 6, 2008 2:23 AM, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On Jan 5, 2008 5:51 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > I would like to get an IO 1.4 release out in the near future. Looking
> > thru the issues tagged for 1.4 I would suggest the following:
> >
> > 1) Resolve the fo
> -Original Message-
> From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 05, 2008 5:52 PM
> To: Commons Developers List
> Subject: [IO] Planning IO 1.4 release
>
> I would like to get an IO 1.4 release out in the near future. Looking
> thru the issues tagged for 1.4
On Jan 5, 2008 5:51 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> I would like to get an IO 1.4 release out in the near future. Looking
> thru the issues tagged for 1.4 I would suggest the following:
>
> 1) Resolve the following issues, which all have patches except IO-149
> which is trivial
>
I would like to get an IO 1.4 release out in the near future. Looking
thru the issues tagged for 1.4 I would suggest the following:
1) Resolve the following issues, which all have patches except IO-149
which is trivial
IO-149 - Make FilenameUtils.EXTENSION_SEPARATOR public
IO-105 - Add a FileU
Phil Steitz wrote:
Yes. It may be ultimately best to make this configurable. If you are
OK with this approach, what I suggest is that you open a JIRA ticket,
attaching a version of your patch that supports configurability. Open
the ticket against 1.3 for now but keep the patch as is (i.e. again
+1 here too.
On Jan 5, 2008 3:08 PM, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Could be too late, but +1 and thanks!
>
>
> On Jan 3, 2008 6:30 AM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > There have been quite a few changes to commons-parent since version 5
> > was released so I'd
Could be too late, but +1 and thanks!
On Jan 3, 2008 6:30 AM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> Hi,
>
> There have been quite a few changes to commons-parent since version 5
> was released so I'd like to release version 6. The changes since the
> last release in summary:
>
> Changes to
> >
> > The 1.2 / 1.4-RC1 code does "recheck" before initiating additional
> > makes - i.e., it will not initiate a makeObject if an idle object has
> > been returned to the pool or if maxActive has been reached. I think I
> > understand your point though, but again it doesn't seem natural to use
On Jan 5, 2008 7:49 AM, <[EMAIL PROTECTED]> wrote:
> Hi Phil,
>
> thanks for taking my issue serious.
>
> Phil Steitz wrote:
>
> > Thanks again for the feedback. Any other opinions / suggestions on
> > this are appreciated. I suggest the following compromise, which would
> > also fix the maxAct
On 11/19/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Nov 19, 2007 5:58 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > New thread:
> >
> > >> Dennis Lundberg wrote:
> > >
> > >>> I'll change this. Should it be changed to "Apache Commons Logging" or
> > >>> simply "Commons Logging"? This i
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34787&projectId=155
Build statistics:
State: Ok
Previous State: Failed
Started at: Sat 5 Jan 2008 09:31:40 -0800
Finished at: Sat 5 Jan 2008 09:32:16 -0800
Total time: 35s
Build Trigger: Schedule
Build Number:
Phil Steitz wrote:
If you are really worried about the cost of object creation then you can
configure the pool to create all the objects at start-up and block until a
free object is available.
That is unfortunately not possible under our current configuration as we
have set up our application
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34770&projectId=155
Build statistics:
State: Failed
Previous State: Ok
Started at: Sat 5 Jan 2008 08:17:53 -0800
Finished at: Sat 5 Jan 2008 08:18:04 -0800
Total time: 11s
Build Trigger: Schedule
Build Number:
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34770&projectId=155
Build statistics:
State: Failed
Previous State: Ok
Started at: Sat 5 Jan 2008 08:17:53 -0800
Finished at: Sat 5 Jan 2008 08:18:04 -0800
Total time: 11s
Build Trigger: Schedule
Build Number:
Hi Phil,
thanks for taking my issue serious.
Phil Steitz wrote:
Thanks again for the feedback. Any other opinions / suggestions on
this are appreciated. I suggest the following compromise, which would
also fix the maxActive exceeded by one issue I discovered with
1.2/1.4-RC1 yesterday:
(*)
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34739&projectId=165
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:02:09 -0800
Finished at: Sat 5 Jan 2008 06:02:12 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34739&projectId=165
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:02:09 -0800
Finished at: Sat 5 Jan 2008 06:02:12 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34738&projectId=163
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:55 -0800
Finished at: Sat 5 Jan 2008 06:01:59 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34738&projectId=163
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:55 -0800
Finished at: Sat 5 Jan 2008 06:01:59 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34737&projectId=162
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:42 -0800
Finished at: Sat 5 Jan 2008 06:01:45 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34737&projectId=162
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:42 -0800
Finished at: Sat 5 Jan 2008 06:01:45 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34736&projectId=22
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:29 -0800
Finished at: Sat 5 Jan 2008 06:01:32 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34736&projectId=22
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:29 -0800
Finished at: Sat 5 Jan 2008 06:01:32 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34735&projectId=161
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:12 -0800
Finished at: Sat 5 Jan 2008 06:01:16 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34735&projectId=161
Build statistics:
State: Error
Previous State: Ok
Started at: Sat 5 Jan 2008 06:01:12 -0800
Finished at: Sat 5 Jan 2008 06:01:16 -0800
Total time: 3s
Build Trigger: Schedule
Build Number: 0
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34734&projectId=176
Build statistics:
State: Error
Previous State: Failed
Started at: Sat 5 Jan 2008 06:00:37 -0800
Finished at: Sat 5 Jan 2008 06:01:00 -0800
Total time: 23s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=34734&projectId=176
Build statistics:
State: Error
Previous State: Failed
Started at: Sat 5 Jan 2008 06:00:37 -0800
Finished at: Sat 5 Jan 2008 06:01:00 -0800
Total time: 23s
Build Trigger: Schedule
Build Numbe
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
Any opinions on which way to go with
http://issues.apache.org/jira/browse/LANG-381 would be very much
appreciated.
Currently my instinct is to go with making min/max obey the JDK - ie)
old IEEE, and adding a IEEE754rUtils class with its own set of methods
for the new way.
I'll go ahead and code t
30 matches
Mail list logo
