[jira] [Commented] (SLING-6992) Switch back to JRE 6 for discovery.commons

["Stefan Egli (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072354#comment-16072354 ] 

Stefan Egli commented on SLING-6992:
------------------------------------

Turns out JRE 6 won't work anymore due to [johnzon|https://github.com/apache/sling/tree/trunk/bundles/commons/johnzon] requiring JRE 7 (and for some reason {{mvn release:prepare release:perform}} didnt pick this up).

So this means the discovery bundles now require JRE 7 too.

I'll undo staging 1749 (containing discovery.commons 1.0.22, discovery.base 2.0.2) and revert 1800639 (and 1800652), leaving discovery.commons 1.0.20 as the latest for now and releasing discovery.base 2.0.4 (with JRE 7 dependendy and requiring commons 1.0.20 instead)

> Switch back to JRE 6 for discovery.commons
> ------------------------------------------
>
>                 Key: SLING-6992
>                 URL: https://issues.apache.org/jira/browse/SLING-6992
>             Project: Sling
>          Issue Type: Task
>          Components: Extensions
>    Affects Versions: Discovery Commons 1.0.20
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Commons 1.0.22
>
>
> SLING-6837 increased the parent version from 26 to 30 and with that uped the JRE version from 6 to 7. To simplify maintenance for older (eg AEM) users of discovery it would be good to stay with JRE 6 as long as feasible.
> To achieve this, discovery.commons should just overwrite the {{sling.java.version}} property back to {{6}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)