commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [ALL] JDK 9 Version String
Date Thu, 14 Jul 2016 18:05:48 GMT
Am I blind or can someone point out how to comment on a JEP? The JEP is
linked to but how do you
get an account on that?

I recall hearing a preso on how the comments for Java were locked down for
fear of too much feedback... or something.


On Thu, Jul 14, 2016 at 8:24 AM, Paul Benedict <> wrote:

> If this issue has been raised in the past, my apologies. I did a search for
> "Verona" in the mail archives here and didn't see any hit besides Oracle's
> own notification [1]. That was the only hit.
> In JDK 9, the version string is changing from 1.0.X to bigger numbers like
> 9.0.0 [2]. Code that has assumed the 1.x pattern for parsing the version
> string will likely fail or behave strangely. Apache Commons will be one of
> these libraries [3]. I already notified the Log4J community that Log4J 1.x
> is also affected. So this is just an FYI for any Commons project that is
> relying on the Version string.
> The slew of Apache Commons sub-projects are likely baked into many
> applications. So what does Verona's change mean in practice to all you
> here? Any concerns on Verona? This is the time to speak up to Oracle with
> any feedback you may have.
> [1]
> [2]
> [3]
> Cheers,
> Paul

E-Mail: |
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message