commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SCXML-248) Java 7 support for commons-scxml2
Date Sun, 10 Dec 2017 21:58:00 GMT

     [ https://issues.apache.org/jira/browse/SCXML-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma closed SCXML-248.
---------------------------
    Resolution: Won't Fix

> Java 7 support for commons-scxml2
> ---------------------------------
>
>                 Key: SCXML-248
>                 URL: https://issues.apache.org/jira/browse/SCXML-248
>             Project: Commons SCXML
>          Issue Type: Wish
>    Affects Versions: 2.0
>            Reporter: Yuriy Flyud
>
> commons-scxml2 project is compiled with Java 8. Attempts to compile sources with Java
7 fail because of usage of lambda expressions, etc. The problem number two is usage of JDK
8+ Nashorn Script Engine in JSEvaluator that is not available in JDK 7 (the one with Rhino).
Tests for JSEvaluator fail on Java 7.
> The good news is that all the Java 8 specific features are used only in the env.groovy
package, and Script Engine Replacement issue affects only env.javascript package. All the
core functionality can work, and actually works, with Java 7.
> I propose to extract the core functionlaity from the commons-scxml2 to something like
commons-scxml2-core, and make it Java 7 compatible.
> There are currently no any known stable SCXML Engine implementations that support latest
SCXML specification, so disabling the Java 7 compliance forbids many developers like me to
use it in their products.
> From my side I can propose creating a fork on Git repository for Java 7 compatible commons-scxml2
project in case you decide to leave everything as it is.



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

Mime
View raw message