You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2016/10/14 19:55:20 UTC
[jira] [Commented] (NIFI-2154) ExecuteScript: Fails to load Groovy
Class Path from ExecuteScript nar
[ https://issues.apache.org/jira/browse/NIFI-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576325#comment-15576325 ]
Matt Burgess commented on NIFI-2154:
------------------------------------
Which import statements are failing? As far as I know, many people are using Groovy with ExecuteScript (in 0.6.1 and beyond) without trouble.
> ExecuteScript: Fails to load Groovy Class Path from ExecuteScript nar
> ---------------------------------------------------------------------
>
> Key: NIFI-2154
> URL: https://issues.apache.org/jira/browse/NIFI-2154
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Environment: CentOS
> Reporter: Christopher Reeves
> Labels: easyfix, patch
>
> The ExecuteScript processor is failing to load the classpath for the groovy-all jar file from the ExecuteScript nar which causes import statements within the groovy script to fail.
> A workaround exists by copying the groovy-all jar file to the lib directory of nifi base directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)