Issue:
We have installed TIBCO Jaspersoft® Studio v8.0.0 in our Development environment but when trying to compile the existing reports, the following error was encountered:
java.lang.RuntimeException: BUG! exception in phase 'semantic analysis' in source unit
This problem did not occur in the previous release of Jaspersoft Studio v7.5.0.The log file captures the following stack:
java.lang.RuntimeException: BUG! exception in phase 'semantic analysis' in source unit 'calculator_Inventory_By_Lot_Report_1639377271574_599629' null at net.sf.jasperreports.eclipse.builder.JasperReportCompiler.compileReport(JasperReportCompiler.java:307) Caused by: BUG! exception in phase 'semantic analysis' in source unit 'calculator_Inventory_By_Lot_Report_1639377271574_599629' null at org.codehaus.groovy.control.CompilationUnit$ISourceUnitOperation.doPhaseOperation(CompilationUnit.java:905) Caused by: groovy.lang.GroovyRuntimeException at org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:72) at org.codehaus.groovy.control.ClassNodeResolver.findDecompiled(ClassNodeResolver.java:251) Caused by: java.net.URISyntaxException: Illegal character in opaque part at index 46: jar:file:/D:/Softwares/JS_INSTALL/Licensing Security Files_30-Apr-2020/abc-scriptlet-1.0.1.jar!/com/abc/JasperLicenseValidator.class at java.base/java.net.URI$Parser.fail(Unknown Source) at java.base/java.net.URI$Parser.checkChars(Unknown Source) at java.base/java.net.URI$Parser.parse(Unknown Source) at java.base/java.net.URI.<init>(Unknown Source) at java.base/java.net.URL.toURI(Unknown Source) at org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:70) ... 76 more
Solution:
The error is due to groovy libraries similar to this article below:
https://gateway.sdl.com/apex/communityknowledge?articleName=000016521
where the cause of the problem is due to spaces in the PATH.
In TIBCO Jaspersoft® Studio 8.0, the groovy and java libraries have both been updated and hence it is possible that newer versions may have issues with the spaces in the path.
To resolve this problem, eliminate the spaces in the PATH (spaces are visible in "Licensing Security Files_30-Apr-2020") and do the compilation again.
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now