[
http://jira.codehaus.org/browse/MOJO-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Tran closed MOJO-886.
-------------------------
Assignee: Dan Tran
Resolution: Won't Fix
You will need to precompile the needed classes first before the jrxml files are
processed ( default at generate-sources phase)
see http://jira.codehaus.org/browse/MOJO-1114 for an example on how configure
the precompilation
> jasperreports:compile-reports does not recognize variable types from project
> when bound to compile
> --------------------------------------------------------------------------------------------------
>
> Key: MOJO-886
> URL: http://jira.codehaus.org/browse/MOJO-886
> Project: Mojo
> Issue Type: Bug
> Components: jasperreports
> Environment: java 1.5, JasperReports 1.3.4,
> jasperreports-maven-plugin 1.0-SNAPSHOT (8/15/07)
> Reporter: Jessie Crowe
> Assignee: Dan Tran
> Attachments: jasperreports_test.zip
>
>
> When binding the jasperreports plugin to the compile phase of a module, you
> can reference module classes in the report, but not declare report variables
> of these types. Attached is a simple test case that demonstrates this.
> Please unzip the simple project and use "mvn install". You will see that one
> report compiles, while the other fails. Please note that when these reports
> are compiled at runtime, they both work fine.
--
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
