Re: using jdk 6 class in a sling patch

[Felix Meschberger <fm...@adobe.com>]

(Moving Dev discussions to the Dev list)

Hi Amit,

IIRC we had discussions before, but at that time decided to stick with Java 5. Times are changing, Java 5 is vanishing, Java 6 being EOL-ed, ...

I think we should pick this discussion up again and say:

  * Java 5 by default
  * Java 6 acceptable (requiring appropriate
      Bundle-RequiredExceutionEnvironment setup and API checks)
  * Launchpad will require Java 6 in the future

WDYT ?

Regards
Felix

Am 23.11.2012 um 12:00 schrieb Amit.. Gupta.:

> Hi Guys,
> 
> I am working on a sling patch and planning to use a JDK6 class [0].
> 
> What is the min JDK requirement for sling? Are we planning to move to JDK6?
> 
> Thanks,
> Amit
> [0] http://docs.oracle.com/javase/6/docs/api/index.html?java/util/concurrent/ConcurrentSkipListMap.html

Re: using jdk 6 class in a sling patch

[Chetan Mehrotra <ch...@gmail.com>]

> +1 to Felix suggestion but we should reduce the use of Java 6 to a
> minimum, e.g. SLING-2575 is about our commons osgi bundle which is
> used in a lot of places.

Agreed ... it should preferably be used for new bundles. Old bundles
should not make use of JDK 6 unless really required.

As for SLING-2575 - The JDK 6 requirement is not to include that
patch. Instead it is required to use the approach proposed in that
patch (see the last few comments). So we do not change the commons
bundle but instead users can use new ConcurrentSkipListMap to manage
ordered list of references based on service ranking.

Chetan Mehrotra

Re: using jdk 6 class in a sling patch

[Carsten Ziegeler <cz...@apache.org>]

+1 to Felix suggestion but we should reduce the use of Java 6 to a
minimum, e.g. SLING-2575 is about our commons osgi bundle which is
used in a lot of places. If we require this to use Java 6 this will
require all bundles using this one to be Java 6.

Carsten

2012/11/27 Chetan Mehrotra <ch...@gmail.com>:
> +1
>
> For new bundles it should be possible to make use of JDK 6 API. Two cases I
> require them for
>
> 1. JAAS Support (SLING-2623) - Need to use the new API of ConfigurationSpi
> 2. Managing multiple references (SLING-2575) - Need to use the
> ConcurrentSkipListMap for simplifying usage [1] of multiple references (as
> required by Amit also)
>
> Chetan Mehrotra
> [1] https://gist.github.com/3918574
>
> On Mon, Nov 26, 2012 at 10:36 AM, Amit.. Gupta. <am...@adobe.com> wrote:
>
>> >  * Java 5 by default
>>   * Java 6 acceptable (requiring appropriate
>>       Bundle-RequiredExceutionEnvironment setup and API checks)
>>   * Launchpad will require Java 6 in the future
>>
>> +1
>>
>> Thanks,
>> Amit
>>



-- 
Carsten Ziegeler
cziegeler@apache.org

Re: using jdk 6 class in a sling patch

[Chetan Mehrotra <ch...@gmail.com>]

+1

For new bundles it should be possible to make use of JDK 6 API. Two cases I
require them for

1. JAAS Support (SLING-2623) - Need to use the new API of ConfigurationSpi
2. Managing multiple references (SLING-2575) - Need to use the
ConcurrentSkipListMap for simplifying usage [1] of multiple references (as
required by Amit also)

Chetan Mehrotra
[1] https://gist.github.com/3918574

On Mon, Nov 26, 2012 at 10:36 AM, Amit.. Gupta. <am...@adobe.com> wrote:

> >  * Java 5 by default
>   * Java 6 acceptable (requiring appropriate
>       Bundle-RequiredExceutionEnvironment setup and API checks)
>   * Launchpad will require Java 6 in the future
>
> +1
>
> Thanks,
> Amit
>

RE: using jdk 6 class in a sling patch

["Amit.. Gupta." <am...@adobe.com>]

>  * Java 5 by default
  * Java 6 acceptable (requiring appropriate
      Bundle-RequiredExceutionEnvironment setup and API checks)
  * Launchpad will require Java 6 in the future

+1

Thanks,
Amit

RE: using jdk 6 class in a sling patch

["Amit.. Gupta." <am...@adobe.com>]

>  * Java 5 by default
  * Java 6 acceptable (requiring appropriate
      Bundle-RequiredExceutionEnvironment setup and API checks)
  * Launchpad will require Java 6 in the future

+1

Thanks,
Amit