[
http://jira.codehaus.org/browse/MOJO-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Klein updated MOJO-809:
------------------------------
Attachment: patch.diff
The next one;)
Because jasperreports tries to instantiate the compiler class, which is in the
mojo. We can't do it this way because then the report depends on the
jasperreports-maven-plugin and all the transitive dependencies.
So i seeked for a different solution and made a hack to concatenate some cli
arguments to the classpath string which will be used by the default
JRDefaultCompiler.
I know this is evil, but the jasper interfaces are not designed to pass in such
parameters to force class file versions.
Another solution would be, to build a small package with just an implementation
of JRCompiler and no dependencies to the mojo, with the ability to recognize
such parameters like -target.
It'd also be nice to use the new javax.tools from 1.6 if maven runs under 1.6.
> Added support for selecting target version of the generated class files to
> jasperreports-maven-plugin
> -----------------------------------------------------------------------------------------------------
>
> Key: MOJO-809
> URL: http://jira.codehaus.org/browse/MOJO-809
> Project: Mojo
> Issue Type: Improvement
> Components: jasperreports
> Reporter: Roland Klein
> Priority: Minor
> Attachments: patch.dif, patch.diff, patch.diff
>
>
> Attached patch for rev.4230
> + JRPluginCompiler.java
> * pom.xml
> * JasperReportsMojo.java
--
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
