[
http://jira.codehaus.org/browse/MOJO-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249762#action_249762
]
Mathieu Filotto commented on MOJO-1565:
---------------------------------------
We have the same problem.
Two different JDK on the same OS, and when maven is configured to compile on
the old one 1.5, jasper plugin still compile on the active one 1.6.
> jasper-reports plugin does not take Maven's compiler settings into account
> --------------------------------------------------------------------------
>
> Key: MOJO-1565
> URL: http://jira.codehaus.org/browse/MOJO-1565
> Project: Mojo
> Issue Type: Bug
> Components: jasperreports
> Environment: WindowsXP, Java 1.5 & 1.6, Maven
> Reporter: Tom Eugelink
> Priority: Critical
>
> I have a Maven project that uses both Java 1.6 and 1.5; there is an applet
> that is run under 1.6, but the server backend under 1.5. The project is setup
> as components, each pom specifies which java version to use.
> When the toplevel pom is called which (will build all components), this needs
> to be done under java 1.6, otherwise the applet won't compile correctly. The
> regular java code is compiled as specified in the pom; the applet with 1.6,
> the server side with 1.5. But the Jasper reports seem to be compiled using
> the active java (1.6) and not the specified one (1.5), so I get bad class
> version numbers.
> java.lang.UnsupportedClassVersionError: Bad version number in .class file
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at
> net.sf.jasperreports.engine.util.JRClassLoader.loadClass(JRClassLoader.java:342)
> at
> net.sf.jasperreports.engine.util.JRClassLoader.loadClassFromBytes(JRClassLoader.java:243)
> at
> net.sf.jasperreports.engine.design.JRAbstractJavaCompiler.loadEvaluator(JRAbstractJavaCompiler.java:92)
> at
> net.sf.jasperreports.engine.design.JRAbstractCompiler.loadEvaluator(JRAbstractCompiler.java:320)
> at
> net.sf.jasperreports.engine.JasperCompileManager.loadEvaluator(JasperCompileManager.java:244)
> at
> net.sf.jasperreports.engine.fill.JRFillDataset.createCalculator(JRFillDataset.java:411)
> at
> net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:405)
> at
> net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:77)
> at
> net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:59)
> at
> net.sf.jasperreports.engine.fill.JRFiller.createFiller(JRFiller.java:147)
> at
> net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:57)
> at
> net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:402)
> at
> net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:234)
> at nl.knowledgeplaza.dh.report.Report.doGet(Report.java:170)
> The plugin should either take the specified java version into account or be
> able to acccept compiler version information.
> <!-- setup the compiler -->
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.3.1</version>
> <configuration>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
