+1
Before ages when I wrote the "ChangeSet" stuff I have marked them as
"experimental". Have not heard any complains yet... we should discuss
if we remove that label or if need some more tweaks there. Probably
after 1.4?
On Sat, Mar 31, 2012 at 6:48 AM, Stefan Bodewig wrote:
> Hi all,
>
> Compre
Christian Grobmeier wrote:
> +1
>
> Before ages when I wrote the "ChangeSet" stuff I have marked them as
> "experimental". Have not heard any complains yet... we should discuss
> if we remove that label or if need some more tweaks there. Probably
> after 1.4?
If nobody complained about it until
The trunk looks good now IMO. I'll let others decide about the change set
docs.
The only item that stick out but could wait for another release:
- the large code dup in BZip2CompressorInputStream as noted by CPD.
- the apparently unfinished JarArchiveEntry
- unused summary fields in DumpArchiveEnt
On 31 March 2012 05:48, Stefan Bodewig wrote:
> Hi all,
>
> Compress' trunk has been sitting on valuable content for too long now:
>
> * XZ compression
>
> * BZIP2 now reads streams created by pbzip2 (parallel bzip2)
>
> * TAR has been largely improved to support reading and writing big
> files,
On Mar 31, 2012, at 8:30, sebb wrote:
> On 31 March 2012 05:48, Stefan Bodewig wrote:
>> Hi all,
>>
>> Compress' trunk has been sitting on valuable content for too long now:
>>
>> * XZ compression
>>
>> * BZIP2 now reads streams created by pbzip2 (parallel bzip2)
>>
>> * TAR has been largely imp
On 28 March 2012 17:18, Thomas Neidhart wrote:
> On 03/28/2012 05:46 PM, sebb wrote:
>> On 28 March 2012 15:46, Gilles Sadowski wrote:
> Hello.
>
> Please disable the default running of cobertura in "mvn site". It is
> unbearably slow: e.g. on my machine, "FastMathTest" takes 1,54
On 31 March 2012 05:48, Stefan Bodewig wrote:
> Hi all,
>
> Compress' trunk has been sitting on valuable content for too long now:
>
> * XZ compression
>
> * BZIP2 now reads streams created by pbzip2 (parallel bzip2)
>
> * TAR has been largely improved to support reading and writing big
> files,
I had a look at this issue, but could not come to a conclusion.
A test case for TestVFSConfigurationBuilder is failing. At first I
suspected a recent change in [vfs] would cause the problem. However, I
could locally build [configuration] with the recent [vfs] snapshot
version without any probl
I finally went a looked at this. Why in the world did you comment on a Jira
issue that is closed and not change its status? No one is going to even look
at it.
Ralph
On Feb 15, 2012, at 8:04 AM, Gary Gregory wrote:
> On Wed, Feb 15, 2012 at 10:38 AM, Matt Benson wrote:
>
>> On Wed, Feb 15,
I have real problems with Gump. I find it very difficult to determine what the
problem actually is much less diagnose it. Other than that I know it is
supposed to be using the latest source in trunk it is tough to figure out how
to reproduce a problem as it means manually going to all the depend
From the vfs2 log it looks like it is running into a binary incompatibility
with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn dependency:tree is showing
me that Jackrabbit is referencing jcl-over-slf4j and is using 1.5.3. I've
added that to the vfs2 pom in hopes that Gump will honor it. If it
Good afternoon everyone.
Could someone point me to the process or documentation for proposing and
contributing a new project to the Apache Commons?
--
A better world shall emerge based on faith and understanding - Douglas
MacArthur
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-graph 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-collections4-testframework has an issue affecting its community
i
On 2012-03-31, sebb wrote:
> There are a few places where the default charset is being used.
> It's not clear whether these are intentional or not, so I have marked
> them with TODOs.
Thanks (and thanks for the other fixes as well).
> We should either document that the default is OK, or use a fi
On 2012-03-31, Christian Grobmeier wrote:
> Before ages when I wrote the "ChangeSet" stuff I have marked them as
> "experimental". Have not heard any complains yet... we should discuss
> if we remove that label or if need some more tweaks there. Probably
> after 1.4?
I must admit I've never used
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-scxml-test has an issue affecting its community integration.
This
On 2012-03-31, Gary Gregory wrote:
> The trunk looks good now IMO. I'll let others decide about the change set
> docs.
> The only item that stick out but could wait for another release:
> - the large code dup in BZip2CompressorInputStream as noted by CPD.
I've seen that but must admit I didn't s
On 2012-04-01, Ralph Goers wrote:
> I have real problems with Gump. I find it very difficult to determine
> what the problem actually is much less diagnose it. Other than that I
> know it is supposed to be using the latest source in trunk it is tough
> to figure out how to reproduce a problem as i
On 2012-04-01, Ralph Goers wrote:
> From the vfs2 log it looks like it is running into a binary
> incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn
> dependency:tree is showing me that Jackrabbit is referencing
> jcl-over-slf4j and is using 1.5.3. I've added that to the vfs2 pom
On Mar 31, 2012, at 10:23 PM, Stefan Bodewig wrote:
> On 2012-04-01, Ralph Goers wrote:
>
>> From the vfs2 log it looks like it is running into a binary
>> incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn
>> dependency:tree is showing me that Jackrabbit is referencing
>> jcl-ov
I've looked at this and I simply think testValidation and testValidation2 are
incorrect. I believe their purpose is to test schema validation. If that failed
they would throw an exception. The two asserts after reading the configuration
don't actually validate anything those tests are doing. The
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
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-proxy-test has an issue affecting its community integration.
This
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-id has an issue affecting its community integration.
This issue af
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-vfs2-test has an issue affecting its community integration.
This i
26 matches
Mail list logo
