[
https://issues.apache.org/jira/browse/NIFI-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536185#comment-17536185
]
Paul Grey commented on NIFI-10003:
----------------------------------
I've done a little investigation into this issue. There might be a way to
retain "jython-slim", because of the size savings and the reduced dependency
footprint. But in the interest of time, it seems best to revert to
"jython-standalone".
> NiFi build fails in UTC+ time zones
> -----------------------------------
>
> Key: NIFI-10003
> URL: https://issues.apache.org/jira/browse/NIFI-10003
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Turcsanyi
> Assignee: Paul Grey
> Priority: Major
> Fix For: 1.17.0, 1.16.2
>
>
> nifi-scripting-nar build fails when no user.timezone system property is
> specified (I'm in UTC+2) or a UTC+ timezone is specified (e.g.
> {{{}-Duser.timezone=Europe/Budapest{}}} or {{-Duser.timezone=Asia/Tokyo}})
> for the maven build.
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.nifi:nifi-nar-maven-plugin:1.3.3:nar (default-nar) on project
> nifi-scripting-nar: Failed to create Extension Documentation:
> InvocationTargetException: java.lang.TypeNotPresentException:
> java.lang.TypeNotPresentException: Type org/python/core/PyObject not present:
> org.python.core.PyObject -> [Help 1]
> {code}
> It works properly with {{-Duser.timezone=UTC}} or
> {{-Duser.timezone=America/New_York}}
> The culprit is NIFI-8533, though the root cause is not clear. Nevertheless,
> if I revert that commit, everything works fine in all time zones.
> Workaround: use {{-Duser.timezone=UTC}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
