On Fri, 2015-05-29 at 18:08 +0300, Robert Munteanu wrote:
On May 29, 2015 5:55 PM, Daniel Klco daniel.k...@gmail.com wrote:
Considering that Oracle is already stopped public updates for both
Java 6
and that the Premium Support ends December 2015, it would seem to
make
sense to
not drop Java 6 support for new released bundles at all?
+1 for using Java 7 as default and minimum Java version.
stefan
-Original Message-
From: Robert Munteanu [mailto:romb...@apache.org]
Sent: Thursday, May 28, 2015 11:58 AM
To: dev@sling.apache.org
Subject: Moving to Java 7 ( was: Make
I think we should allow Java 7 but not make it the default. 6 seems more
reasonable. It's like with dependencies to other bundles, we should use
the lowest version that makes sense :) So if there is no reason for
requiring 7 in a module, why should we?
Java 5 is way too old, so I think it doesn't
That would be a good idea. When looking at the AEM 6.1 technical requirements
you can already see there is no more support for Oracle JDK 1.6, minimum Oracle
JDK 1.7
Roy
On 29 May 2015, at 11:23, Stefan Seifert sseif...@pro-vision.de wrote:
it's just that we cannot use features like
Am 29.05.15 um 11:23 schrieb Stefan Seifert:
it's just that we cannot use features like Closeable when we still support
JDK 1.6.
Yepp, that's why I said, if it makes sense for a bundle to be based on
1.7 then we're free to do it.
if we do not want switch to JDK 1.7 now perhaps we should
it's just that we cannot use features like Closeable when we still support JDK
1.6.
if we do not want switch to JDK 1.7 now perhaps we should come up with a
plan/roadmap when to do the switch and document it on the website, then it is
possible for upstream projects to take this into account.
On May 29, 2015 5:55 PM, Daniel Klco daniel.k...@gmail.com wrote:
Considering that Oracle is already stopped public updates for both Java 6
and that the Premium Support ends December 2015, it would seem to make
sense to standardize on Java 7 for new development and change everything
over at
Considering that Oracle is already stopped public updates for both Java 6
and that the Premium Support ends December 2015, it would seem to make
sense to standardize on Java 7 for new development and change everything
over at the end of the year.
Either way this shakes out, we should create a
This might've been buried under the 'Closeable' thread so resending so
that it does not suprise anyone.
Currently our projects can use either Java 5 or 6, with 5 being the
default. This is very much out of date and we're missing out on
language improvements. I would suggest changing the supported
( was: Make ResourceResolver implement Closeable)
This might've been buried under the 'Closeable' thread so resending so
that it does not suprise anyone.
Currently our projects can use either Java 5 or 6, with 5 being the
default. This is very much out of date and we're missing out on
language
10 matches
Mail list logo
