On 11/25/2015 11:30 AM, Jörg Schaible wrote:
> Hi Thomas,
>
> Thomas Neidhart wrote:
>
>> On 11/24/2015 11:30 PM, Jörg Schaible wrote:
>>> Hi Thomas,
>>>
>>> Thomas Neidhart wrote:
>
> [snip]
>
>> These test failures exist since the 4.0 release, quoting your vote for
>> Collection 4.0 based on
On 11/22/2015 11:26 PM, Thomas Neidhart wrote:
> Hi all,
>
> we have accumulated enough changes since the last 4.0 release as well as
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> C
ince the last 4.0 release as well as
>>> we need to provide a fix for the known remote code exploit via java
>>> de-serialization. Therefore, I would like to start a vote to release
>>> Commons Collections 4.1 based on RC1.
>>
>> Thanks for all the people that vot
the known remote code exploit via java
> > de-serialization. Therefore, I would like to start a vote to release
> > Commons Collections 4.1 based on RC1.
>
> Thanks for all the people that voted.
> Some glitches have been found and I also have found myself a few minor
> is
Hi Thomas,
Thomas Neidhart wrote:
> On 11/24/2015 11:30 PM, Jörg Schaible wrote:
>> Hi Thomas,
>>
>> Thomas Neidhart wrote:
[snip]
> These test failures exist since the 4.0 release, quoting your vote for
> Collection 4.0 based on RC5:
>
>> +1, builds for all but one JDK flawlessly from
-serialization. Therefore, I would like to start a vote to release
Commons Collections 4.1 based on RC1.
Note:
The fix for the security related issue results in Clirr errors as
unsafe
classes in the functor package do not implement the Serializable
interface anymore. This is mentioned in the release notes
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now, i.e. after 2400
> GMT 25-November 2015
+1
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
Hi Thomas,
Thomas Neidhart wrote:
> Hi all,
>
> we have accumulated enough changes since the last 4.0 release as well as
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> Commons Col
On 11/22/2015 11:26 PM, Thomas Neidhart wrote:
> Hi all,
>
> we have accumulated enough changes since the last 4.0 release as well as
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> C
de-serialization. Therefore, I would like to start a vote to release
>> Commons Collections 4.1 based on RC1.
>>
>> Note:
>>
>> The fix for the security related issue results in Clirr errors as unsafe
>> classes in the functor package do not implement
> we need to provide a fix for the known remote code exploit via java
> de-serialization. Therefore, I would like to start a vote to release
> Commons Collections 4.1 based on RC1.
>
> Note:
>
> The fix for the security related issue results in Clirr errors as unsafe
>
On 11/23/2015 09:53 PM, Oliver Heger wrote:
> The Maven build worked fine with Java 1.6 and 1.7 on Windows 10. With
> Java 1.8 I get the following compilation error in test classes:
>
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
>
Hi all,
we have accumulated enough changes since the last 4.0 release as well as
we need to provide a fix for the known remote code exploit via java
de-serialization. Therefore, I would like to start a vote to release
Commons Collections 4.1 based on RC1.
Note:
The fix for the security related
13 matches
Mail list logo
