I just upgraded to 1.0-rc-1 and all is well except for one unit test failing due to it trying to compile a JasperReport (JasperCompileManager.compileReportToFile(…)) and not being able to find the Jasper JAR. I believe this is directly related to the “Classpath changes for test process” entry in the Release Notes.
From the Jasper docs (http://fecplanner.com/jasperreports/docs/quick.how.to.html): jasper.reports.compile.class.path
By default, JasperReports uses the current JVM classpath to compile the report class (java.class.path system property). To customize this report compilation process, JasperReports lets you override the default behavior by supplying a value to the jasper.reports.compile.class.path system property, which will be used as classpath for the report class compilation.
My problem is that I’m not sure how to follow the Release Notes advice and have Jasper “look for jars loaded via manifest Class-Path entries as well.”
Any hints would be greatly appreciated.