Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1827
The issue is that `jython` uses a binary build instead of Maven so it is an
"unshaded JAR" (described in far more detail
[here](https://github.com/scijava/jython-shaded)). It includes libraries that
conflict with `jruby` but Maven can't resolve them, so there are runtime
errors.
Rather than separate the dependencies into separate modules, we can use the
`jython-shaded` dependency mentioned above to resolve this.
I can't push the changes to this branch, but you can make the following
changes in `nifi-scripting-processor/pom.xml`:
```
<dependency>
<groupId>org.python</groupId>
<artifactId>jython-standalone</artifactId>
<version>2.7.1b3</version>
</dependency>
```
with
```
<dependency>
<groupId>org.scijava</groupId>
<artifactId>jython-shaded</artifactId>
<version>2.7.0</version>
</dependency>
```
Tests all pass:
```
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.nifi.processors.script.ExecuteScriptGroovyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.533 sec -
in org.apache.nifi.processors.script.ExecuteScriptGroovyTest
Running org.apache.nifi.processors.script.TestExecuteClojure
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.029 sec -
in org.apache.nifi.processors.script.TestExecuteClojure
Running org.apache.nifi.processors.script.TestExecuteGroovy
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.648 sec
- in org.apache.nifi.processors.script.TestExecuteGroovy
Running org.apache.nifi.processors.script.TestExecuteJavascript
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.979 sec -
in org.apache.nifi.processors.script.TestExecuteJavascript
Running org.apache.nifi.processors.script.TestExecuteJRuby
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.77 sec -
in org.apache.nifi.processors.script.TestExecuteJRuby
Running org.apache.nifi.processors.script.TestExecuteJython
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.72 sec -
in org.apache.nifi.processors.script.TestExecuteJython
Running org.apache.nifi.processors.script.TestExecuteLua
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec -
in org.apache.nifi.processors.script.TestExecuteLua
Running org.apache.nifi.processors.script.TestInvokeGroovy
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.517 sec -
in org.apache.nifi.processors.script.TestInvokeGroovy
Running org.apache.nifi.processors.script.TestInvokeJavascript
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.396 sec -
in org.apache.nifi.processors.script.TestInvokeJavascript
Running org.apache.nifi.processors.script.TestInvokeJython
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.263 sec -
in org.apache.nifi.processors.script.TestInvokeJython
Running org.apache.nifi.record.script.ScriptedReaderTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.515 sec -
in org.apache.nifi.record.script.ScriptedReaderTest
Running org.apache.nifi.record.script.ScriptedRecordSetWriterTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.24 sec -
in org.apache.nifi.record.script.ScriptedRecordSetWriterTest
Running org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.269 sec -
in org.apache.nifi.reporting.script.ScriptedReportingTaskGroovyTest
Results :
Tests run: 45, Failures: 0, Errors: 0, Skipped: 1
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
