Running old compiler in latest Studio

We are working with software which includes jasperreports 6.3.1. When building jrxml it would be great if we could use the latest Studio and then validate that the report works in 6.3.1 within the designer. Basically studio seems to support this functionality by enabling user to set the compiler. However If I try to do this (latest studio build, download jasperreports 6.3.1 project from sourceforge, add it to studio as new compiler, and set the project to use that as compiler) I get

java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not initialize class net.sf.jasperreports.engine.DefaultJasperReportsContext
    at net.sf.jasperreports.eclipse.builder.JasperReportCompiler.compileReport(JasperReportCompiler.java:131)
    at net.sf.jasperreports.eclipse.builder.JasperReportsBuilder.compileJRXML(JasperReportsBuilder.java:212)
    at com.jaspersoft.studio.editor.action.CompileAction.actionCompile(CompileAction.java:154)

My understanding is that when studio starts to compile, the latest version calls that class, it can't find it in classpath as that is bundled into jasperreports.jar and 6.3.1 doesn't have that. Including jasperreports-6.14.0.jar into classpath feels a bit risky. As the main idea is to validate that the report builds in 6.3.1.

Any clever tips to get that particular setup working, or should we just use studio 6.3.1?

antti.kauhanen's picture
Joined: Nov 11 2014 - 12:19am
Last seen: 2 months 2 weeks ago

Someone suggest this issue!

hongming8888 - 1 year 9 months ago

0 Answers:

No answers yet
Feedback