You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/04/01 15:54:00 UTC
[jira] [Commented] (NIFI-9854) Stateless System Tests cannot be run from IntelliJ
[ https://issues.apache.org/jira/browse/NIFI-9854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515979#comment-17515979 ]
ASF subversion and git services commented on NIFI-9854:
-------------------------------------------------------
Commit 2e66cf711469da804a60bcd596a10ea8ea5afb0a in nifi's branch refs/heads/NIFI-9854 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2e66cf7 ]
NIFI-9854: Include slf4j-api as runtime scope for nifi-stateless-system-test-suite; When constructing the classes to block for the stateless ClassLoader, allow through any classes that come from Java Home's lib/ directory
This closes #5920.
Signed-off-by: Peter Turcsanyi <tu...@apache.org>
> Stateless System Tests cannot be run from IntelliJ
> --------------------------------------------------
>
> Key: NIFI-9854
> URL: https://issues.apache.org/jira/browse/NIFI-9854
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.16.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The NiFi Stateless system tests fail with NoClassDefFoundError: java/lang/Object when attempting to run from IntelliJ. They work fine from Maven, however. The problem appears to be related to the way in which IntelliJ constructs the classpath.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)