Sounds like you should file a bug with OpenJDK...
Gary
On Mon, Oct 6, 2014 at 4:46 PM, Thomas Neidhart
wrote:
> On 10/06/2014 07:12 AM, Stefan Bodewig wrote:
> > Hi all,
> >
> > nothing big this time but a few accumulated bug fixes and support for
> > raw DEFLATE streams.
> >
> > Compress 1.9
On 10/06/2014 07:12 AM, Stefan Bodewig wrote:
> Hi all,
>
> nothing big this time but a few accumulated bug fixes and support for
> raw DEFLATE streams.
>
> Compress 1.9 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 6728)
>
Hi,
I'm reading through some of the code in the exception package and noticed the
following description for MathIllegalStateException:
* Base class for all exceptions that signal a mismatch between the
* current state and the user's expectations.
I'm curious as to whether it should be:
* B
+1
Reports look good.
I trust the keys in https://www.apache.org/dist/commons/KEYS
Downloaded the src-zip file and ran: "mvn clean site".
Tested with:
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T16:58:10-04:00)
Maven home: C:\Java\apache-maven-3.2.3
Java version: 1
On 6 October 2014 17:56, Gary Gregory wrote:
> I was about to plus 1 the release when I looked at the asc file and I am
> likely confusing myself. I:
>
> - Downloaded: https://www.apache.org/dist/commons/KEYS
> - Ran (just to get the latest): gpg --import KEYS
> - Ran: gpg --verify commons-compres
I was about to plus 1 the release when I looked at the asc file and I am
likely confusing myself. I:
- Downloaded: https://www.apache.org/dist/commons/KEYS
- Ran (just to get the latest): gpg --import KEYS
- Ran: gpg --verify commons-compress-1.9-src.zip.asc
and got:
gpg: Signature made 10/06/14
On 6 October 2014 12:26, Stefan Bodewig wrote:
> On 2014-10-06, sebb wrote:
>
>> On 6 October 2014 08:16, Stefan Bodewig wrote:
>
Just a note on the GPG key, it might be a good idea to upgrade to a
stronger one. 1024 bits keys are discouraged nowadays.
>
http://www.apache.org/dev/r
Le 04/10/2014 03:59, Gary Gregory a écrit :
> Hi All,
>
> The live [math] site needs to be updated to reflect the change from Svn to
> Git.
I'm on it (both the site and the pom).
best regards,
Luc
>
> Gary
>
-
To unsubscrib
On Mon, 6 Oct 2014 01:48:49 +0530, venkatesha murthy wrote:
I see that this class and other SynchronizedSummaryStatistic class is
using
old style synchronized which synchronizes both reads and writes...so
was
wondering if we should switch to locks for better concurrency on
reads
Does any one
On 2014-10-06, sebb wrote:
> On 6 October 2014 08:16, Stefan Bodewig wrote:
>>> Just a note on the GPG key, it might be a good idea to upgrade to a
>>> stronger one. 1024 bits keys are discouraged nowadays.
>>> http://www.apache.org/dev/release-signing
>> I know, but leaving behind a key that
On 6 October 2014 08:16, Stefan Bodewig wrote:
>
>> Just a note on the GPG key, it might be a good idea to upgrade to a
>> stronger one. 1024 bits keys are discouraged nowadays.
>
>> http://www.apache.org/dev/release-signing
>
> I know, but leaving behind a key that has accumulated signatures over
On 6 October 2014 11:22, Bernd wrote:
> Dont worry, currentTimesMillis does not step backward if the timezone
> changes automatically, as it is in UTC time.
>
> However it does jump if somebody manually corrects the time (or allows NTP
> zu jump the time). Both operations are however a general pro
Dont worry, currentTimesMillis does not step backward if the timezone
changes automatically, as it is in UTC time.
However it does jump if somebody manually corrects the time (or allows NTP
zu jump the time). Both operations are however a general problem on Java
servers, should be avoided.
If you
On 2014-10-06, Emmanuel Bourg wrote:
> Le 06/10/2014 09:16, Stefan Bodewig a écrit :
>> I know, but leaving behind a key that has accumulated signatures over
>> more than ten years is hard ...
> My suggestion was actually a subtle plan to get you to invite us to
> drink a beer and sign your new
Hi,
Jacopo Cappellato wrote:
>
> On Oct 6, 2014, at 2:31 AM, sebb wrote:
>
>>> The only way to do it is to make
>>> lastReturnTime field thread-safe using locks.
>>
>> Volatile does make the field thread-safe.
>> It's just a question of whether the JVM can re-order the statements
>> when vola
Le 06/10/2014 09:16, Stefan Bodewig a écrit :
> I know, but leaving behind a key that has accumulated signatures over
> more than ten years is hard ...
My suggestion was actually a subtle plan to get you to invite us to
drink a beer and sign your new key :)
Emmanuel Bourg
-
> Just a note on the GPG key, it might be a good idea to upgrade to a
> stronger one. 1024 bits keys are discouraged nowadays.
> http://www.apache.org/dev/release-signing
I know, but leaving behind a key that has accumulated signatures over
more than ten years is hard ...
Stefan
--
Le 06/10/2014 07:12, Stefan Bodewig a écrit :
> [X] +1 Release these artifacts
Tested on Window with Java 7. Changes are ok, Signatures are ok.
Just a note on the GPG key, it might be a good idea to upgrade to a
stronger one. 1024 bits keys are discouraged nowadays.
http://www.apache.org/dev/
18 matches
Mail list logo
