Hi Kristian,
Kristian Rosenvold wrote:
> The Charset related tests fail due some character set that is installed in
> your environment that is nor present in mine (commons.io builds fine on
> IBM jdk6 & 7 here). To try to identify which character set we're talking
> about I added the name to the
The Charset related tests fail due some character set that is installed in
your environment that is nor present in mine (commons.io builds fine on IBM
jdk6 & 7 here). To try to identify which character set we're talking about
I added the name to the assert message; there is already logic in place i
On 28 November 2015 at 20:13, Phil Steitz wrote:
> On 11/28/15 12:02 PM, Jörg Schaible wrote:
>> Phil Steitz wrote:
>>
>>>
>>>
On Nov 27, 2015, at 7:35 PM, Gary Gregory wrote:
Are you saying that the jar in the bin zip includes classes that are
instrumented for use with Cobert
On 11/28/15 12:02 PM, Jörg Schaible wrote:
> Phil Steitz wrote:
>
>>
>>
>>> On Nov 27, 2015, at 7:35 PM, Gary Gregory wrote:
>>>
>>> Are you saying that the jar in the bin zip includes classes that are
>>> instrumented for use with Cobertura? If so, that would be a -1 indeed.
>>>
>> Yes, looks lik
Phil Steitz wrote:
>
>
>
>> On Nov 27, 2015, at 7:35 PM, Gary Gregory wrote:
>>
>> Are you saying that the jar in the bin zip includes classes that are
>> instrumented for use with Cobertura? If so, that would be a -1 indeed.
>>
> Yes, looks like it. New need to find a way to get rid of this
> On Nov 27, 2015, at 7:35 PM, Gary Gregory wrote:
>
> Are you saying that the jar in the bin zip includes classes that are
> instrumented for use with Cobertura? If so, that would be a -1 indeed.
>
Yes, looks like it. New need to find a way to get rid of this thing in cp or
whatever is dragg
Are you saying that the jar in the bin zip includes classes that are
instrumented for use with Cobertura? If so, that would be a -1 indeed.
Gary
On Fri, Nov 27, 2015 at 1:23 PM, Phil Steitz wrote:
> Sigs, hashes, contents look good except for dreaded error below.
> Ant and maven build works fin
Sigs, hashes, contents look good except for dreaded error below.
Ant and maven build works fine on OSX 1.7. Did not test 1.6 or 1.8
yet because of two blockers
1. The binary jar appears to have the dreaded Coberta disease.
When I hack the ant build to run the tests against the release jar,
I ge
Kristian Rosenvold wrote:
> We have fixed quite a few bugs and added some significant
> enhancements since commons-io was released,
> so I would like to release commons-io 2.5
>
> Foo 2.5 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/io/ (svn revisio
I had the same maven errors while working on IO-487, but I assumed it
was because my local copy was not set up correctly.
The TailerTest fails intermittently with or without Cobertura.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 11/24/2015 5:36 PM, Gary Gregory wrote:
Just to
Thanks for the reviews, I'll fix the reported problems and respin!
the test failure on java8 site looks weird, I'll look into that.
As for actually publishing the site on java8, I'd have to switch to
the google BCEL to fix that. I'm assuming we can just "not support"
this for the time being ?
Kr
Just to add to Java 8 woes, running "mvn clean site", I get:
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 08:01 min
[INFO] Finished at: 2015-11
Hi Kristian,
while checking the release I found some problems:
* The commons-io-2.5.jar in the binary distribution contains a
cobertura.properties file. This is probably created by running the site
build over the release build before creating the distributions. In the
past we had a problematic re
We have fixed quite a few bugs and added some significant
enhancements since commons-io was released,
so I would like to release commons-io 2.5
Foo 2.5 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/ (svn revision 11266)
Maven artifacts are here:
14 matches
Mail list logo
