You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2021/06/03 12:13:00 UTC
[jira] [Commented] (SLING-7561) Java Script Handler should fall
back to 'auto' JVM source and target if requested version is not supported
[ https://issues.apache.org/jira/browse/SLING-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356393#comment-17356393 ]
Radu Cotescu commented on SLING-7561:
-------------------------------------
[~rombert], wasn't this handled via SLING-7365? See https://github.com/apache/sling-org-apache-sling-commons-compiler/blob/4c6b81054eac184f8b6899bd607db0ea4708ae81/src/main/java/org/apache/sling/commons/compiler/impl/EclipseJavaCompiler.java#L241.
> Java Script Handler should fall back to 'auto' JVM source and target if requested version is not supported
> ----------------------------------------------------------------------------------------------------------
>
> Key: SLING-7561
> URL: https://issues.apache.org/jira/browse/SLING-7561
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Scripting Java 2.1.8
>
>
> If the Java Script Handler is configured to use an unsupported or unknown Java version, it should fall back to 'auto', preventing old settings from breaking after changing to a different Java version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)