Skip to content

CompilationException doesn't provide any information about the underlying problem #68

@andrus

Description

@andrus

Say you export JJAVA_STARTUP_SCRIPT= with some errors, then on kernel startup, an exception is thrown and printed in the logs. It provides zero information about the actual problem and doesn't help in debugging.

Exception in thread "main" org.dflib.jjava.execution.CompilationException
	at org.dflib.jjava.execution.CodeEvaluator.evalSingle(CodeEvaluator.java:150)
	at org.dflib.jjava.execution.CodeEvaluator.eval(CodeEvaluator.java:170)
	at org.dflib.jjava.execution.CodeEvaluator.init(CodeEvaluator.java:84)
	at org.dflib.jjava.execution.CodeEvaluator.eval(CodeEvaluator.java:163)
	at org.dflib.jjava.JavaKernel.evalRaw(JavaKernel.java:337)
	at org.dflib.jjava.JavaKernel.eval(JavaKernel.java:342)
	at org.dflib.jjava.JJavaExtension.install(JJavaExtension.java:28)
	at org.dflib.jjava.JavaKernel.handleExtensionLoading(JavaKernel.java:165)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.dflib.jjava.magics.MavenResolver.initImplicitExtensions(MavenResolver.java:119)
	at org.dflib.jjava.JavaKernel.<init>(JavaKernel.java:157)
	at org.dflib.jjava.JJava.main(JJava.java:99)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions