[ https://issues.apache.org/jira/browse/SLING-10691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390609#comment-17390609 ]
Bertrand Delacretaz edited comment on SLING-10691 at 7/30/21, 2:24 PM: ----------------------------------------------------------------------- To experiment with minimal changes for one of these old modules I tried just setting the parent pom version to 43 and adding the missing dependencies versions to the {{sling-org-apache-sling-junit-healthcheck}} module, using the same versions as reported by {{mvn dependency:tree}} before the changes ([commit 571173|https://github.com/apache/sling-org-apache-sling-junit-healthcheck/commit/5711734d9284a2c8ed101ecf2b645e5f4ca5fc6b]) and that build passes now. That won't work for all modules however, for {{org-apache-sling-junit-remote}} for example which uses {{maven-scr-plugin}}, unless I missed something the highest possible parent pom version is 29, which doesn't help with the Java 11 issue. To go higher we'd need to switch away from {{maven-scr-plugin}}. For now, I'll disable sonar builds for that module to have a successful CI build. was (Author: bdelacretaz): To experiment with minimal changes for one of these old modules I tried just setting the parent pom version to 43 and adding the missing dependencies versions to the {{sling-org-apache-sling-junit-healthcheck}} module, using the same versions as reported by {{mvn dependency:tree}} before the changes ([commit 571173|https://github.com/apache/sling-org-apache-sling-junit-healthcheck/commit/5711734d9284a2c8ed101ecf2b645e5f4ca5fc6b]) and that build passes now. That won't work for all modules however, for {{org-apache-sling-junit-remote}} for example which uses {{maven-scr-plugin}}, unless I missed something the highest possible parent pom version is 29, which doesn't help with the Java 11 issue. To go higher we'd need to switch away from {{maven-scr-plugin}}. I'll disable sonar builds for that module to have a successful CI build. > mvn sonar:sonar (Java 11) fails for many modules, "Unable to create javax > script engine for javascript" > ------------------------------------------------------------------------------------------------------- > > Key: SLING-10691 > URL: https://issues.apache.org/jira/browse/SLING-10691 > Project: Sling > Issue Type: Bug > Reporter: Bertrand Delacretaz > Priority: Major > > This error at > https://ci-builds.apache.org/job/Sling/view/Monitor/job/modules/job/sling-maven-launchpad-plugin/job/master/56/console > seems to be common to many of our modules, for which {{mvn sonar:sonar}} > fails on Jenkins: > {code} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.8:run > (set-bundle-required-execution-environment) on project maven-launchpad-plugin: > An Ant BuildException has occured: > Unable to create javax script engine for javascript > [ERROR] around Ant part ... > <script language="javascript">var System = java.lang.System;... @ 4:33 > in > /home/jenkins/workspace/ng-maven-launchpad-plugin_master/target/antrun/build-main.xml > ... > Marking build unstable due to mvn sonar:sonar failing. See > https://cwiki.apache.org/confluence/display/SLING/SonarCloud+analysis for > more info. > {code} > Running {{mvn help:effective-pom}} on the {{}} module which is also failing > shows the below code which is apparently the culprit. > {code} > <execution> > <id>set-bundle-required-execution-environment</id> > ... > <target> > <script language="javascript">var System = java.lang.System; > var bree = "JavaSE-1.6"; > ... > {code} > This looks related to MANTRUN-200 and those builds have been failing for a > while, > https://ci-builds.apache.org/job/Sling/view/Monitor/job/modules/job/sling-org-apache-sling-jcr-jcr-wrapper/job/master/47/ > from June 8 for example has the same problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)