exceptionfactory commented on code in PR #10640:
URL: https://github.com/apache/nifi/pull/10640#discussion_r2619602158
##########
nifi-extension-bundles/nifi-jolt-bundle/nifi-jolt-processors/src/test/java/org/apache/nifi/processors/jolt/TestJoltTransformRecord.java:
##########
@@ -55,14 +55,18 @@
import java.util.function.BiFunction;
import java.util.stream.Stream;
+import org.apache.commons.io.FileUtils;
+
import static org.junit.jupiter.api.Assertions.assertEquals;
-import static org.junit.jupiter.api.Assertions.assertNotNull;
import static org.junit.jupiter.api.Assertions.assertTrue;
public class TestJoltTransformRecord {
final static String CHAINR_SPEC_PATH =
"src/test/resources/specs/chainrSpec.json";
- static String chainrSpecContents;
+ private static final String CUSTOM_CLASS_NAME =
"org.apache.nifi.processors.jolt.TestCustomJoltTransform";
+ private static String chainrSpecContents;
+ private static Path customTransformJar;
+ private static final Path CUSTOM_JAR_DIRECTORY = Paths.get("target",
"test-custom-jolt", "record");
Review Comment:
Thanks for the link. The failure on Windows makes some sense if there is
still an open file reference to the JAR, preventing the delete on Windows. That
actually raises a question about the class loading behavior, which seems to
warrant some additional investigation. It could be a runtime behavior problem,
or it could be something more expected with the custom class loader.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
