Hi Phil,
why are there still 20 issues in JIRA marked as resolved instead of closed
now?
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310485&status=5
- Jörg
Phil Steitz wrote at Donnerstag, 6. August 2009 03:17:
> This vote has passed with no +-0 or -1 votes and +
Hello Apache Development Community,
I would like to propose the following addition to the Commons IO project. I
created a file filter that could read "magic numbers", which are the bytes
(usually but not always at the beginning of a file) that identify a specific
file format. For instance, the Jav
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 gene...@gump.apache.org.
Project commons-jelly-tags-jaxme has an issue affecting its community
integration
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 gene...@gump.apache.org.
Project commons-jelly-tags-fmt-test has an issue affecting its community
integrat
[X] +1 Yes go ahead an release based on RC4
Tested -src.zip with ant and mvn builds on Sun Java 1.6.0_15 on Windows XP
32-bits.
Gary
PS Nits:
I just noticed this in the Ant build output:
[javadoc]
C:\test\commons-codec-1.4-src\src\java\org\apache\commons\codec\digest\DigestUtils.java:68:
wa
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 gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
Niall Pemberton a écrit :
> I have prepared a fourth release candidate for Codec 1.4 following the
> feedback from the third.
>
> [ ] +1 Yes go ahead an release based on RC4
> [ ] -1 No, because...
+1
I'm really impressed by test coverage, its amazing!
Luc
>
> The tag for RC4 is here:
> http:
+1
Niall
On Thu, Aug 6, 2009 at 6:02 PM, Niall
Pemberton wrote:
> I have prepared a fourth release candidate for Codec 1.4 following the
> feedback from the third.
>
> [ ] +1 Yes go ahead an release based on RC4
> [ ] -1 No, because...
>
> The tag for RC4 is here:
> http://svn.apache.org/viewvc/c
On Thu, Aug 6, 2009 at 6:13 PM, Gary
Gregory wrote:
> The CLIRR page reminded me that there is no automated way to make sure we
> have added @since 1.4 tags in all the right places.
>
> For example, Hex.DEFAULT_CHARSET_NAME was missing its @since 1.4, now in SVN.
OK, but it missed RC4 - but no bi
The CLIRR page reminded me that there is no automated way to make sure we have
added @since 1.4 tags in all the right places.
For example, Hex.DEFAULT_CHARSET_NAME was missing its @since 1.4, now in SVN.
Gary
> -Original Message-
> From: Niall Pemberton [mailto:niall.pember...@gmail.co
I have prepared a fourth release candidate for Codec 1.4 following the
feedback from the third.
[ ] +1 Yes go ahead an release based on RC4
[ ] -1 No, because...
The tag for RC4 is here:
http://svn.apache.org/viewvc/commons/proper/codec/tags/CODEC_1_4_RC4/
The release artefacts are here
http://p
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Thursday, August 06, 2009 8:55 AM
> To: Commons Developers List
> Subject: Re: [codec] Are we ready for Codec 1.4 RC4?
>
> On 06/08/2009, Gary Gregory wrote:
> > > -Original Message-
> > > From: sebb [mailto:seb.
>
> In this particular case, the array is package protected, and as such
> surely does not form part of the _public_ API?
>
> If we are not changing it to private now, perhaps we should add a
> comment to say the array will be made private in a future release?
>
Hi, Sebb,
Some users are crazy. S
On 06/08/2009, Gary Gregory wrote:
> > -Original Message-
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: Thursday, August 06, 2009 6:43 AM
> > To: Commons Developers List
> > Subject: Re: [codec] Are we ready for Codec 1.4 RC4?
> >
> > On 06/08/2009, Niall Pemberton wrote:
> >
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Thursday, August 06, 2009 6:43 AM
> To: Commons Developers List
> Subject: Re: [codec] Are we ready for Codec 1.4 RC4?
>
> On 06/08/2009, Niall Pemberton wrote:
> > Are there any more changes people want to do before cutt
Hi!
Using weak ref as default seems not too bad. However, since the file objects
have just their parent cached it might lead to much more file system access
then now as a parent might need to refresh its children.
I tried to kick a discussion about caching at all already [1].
I still think goi
Hi, Niall,
There's my extremely minor CODEC-86 nitpick, but I don't think any
codec committers are interested, so I'm good! I've got no changes.
yours,
Julius
On Thu, Aug 6, 2009 at 6:42 AM, sebb wrote:
> On 06/08/2009, Niall Pemberton wrote:
>> Are there any more changes people want to do
On 06/08/2009, Niall Pemberton wrote:
> Are there any more changes people want to do before cutting another
> Codec 1.4 RC?
I just did a quick scan looking for any mutable variables.
There are some variables which ought to be final; these are already
documented as to be treated as final so no pr
Are there any more changes people want to do before cutting another
Codec 1.4 RC?
Niall
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On Thu, Aug 6, 2009 at 12:10 PM, sebb wrote:
> On 06/08/2009, ggreg...@apache.org wrote:
>> Author: ggregory
>> Date: Thu Aug 6 01:30:08 2009
>> New Revision: 801488
>>
>> URL: http://svn.apache.org/viewvc?rev=801488&view=rev
>> Log:
>> [CODEC-55] make all "business" method implementations o
On 06/08/2009, ggreg...@apache.org wrote:
> Author: ggregory
> Date: Thu Aug 6 01:30:08 2009
> New Revision: 801488
>
> URL: http://svn.apache.org/viewvc?rev=801488&view=rev
> Log:
> [CODEC-55] make all "business" method implementations of public API thread
> safe.
>
> Modified:
>
> c
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 gene...@gump.apache.org.
Project commons-compress-test has an issue affecting its community integration.
Th
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 gene...@gump.apache.org.
Project commons-lang3 has an issue affecting its community integration.
This issue
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 gene...@gump.apache.org.
Project commons-configuration has an issue affecting its community integration.
Th
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 gene...@gump.apache.org.
Project commons-betwixt has an issue affecting its community integration.
This iss
Hi gang,
the docs of VFS praise VFS.getManager() as simplest possibility to work with
VFS. However, this setup uses a SortRefFileCache as default implementation.
This caused our server app to fail, since it means that FileObject
instances are only garbage collected if the Java process runs out of
On Wed, Aug 5, 2009 at 6:23 PM, Julius Davies wrote:
>
> Henri seems pretty busy these days.
On that note
2009's actually been a very active year for me code wise:
http://www.svnsearch.org/svnsearch/repos/ASF/search?from=20090101&to=20091231&author=bayard
Split generally between Taglibs and
27 matches
Mail list logo
