[
http://jira.codehaus.org/browse/MOJO-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Sakar updated MOJO-1141:
-----------------------------
Attachment: patch.txt
The problem actually is hidden in jasperreports - how they handle classloaders.
By debugging and looking at their ant task I've found the current thread
context classloader has to be set as well with classpath used to compile the
report - they use this classloader for report design checks before actual
compilation... Well what to say more, it took me one long evening, hope it will
help.
> Jasperreports plugin can't compile when the jrxml uses a class from one of
> the project dependencies
> ---------------------------------------------------------------------------------------------------
>
> Key: MOJO-1141
> URL: http://jira.codehaus.org/browse/MOJO-1141
> Project: Mojo
> Issue Type: Improvement
> Components: jasperreports
> Environment: windows XP
> Reporter: Geoffrey De Smet
> Attachments: patch.txt
>
>
> The plugin does build a correct classpath with buildClasspathString(), for
> example:
> d:\projects\ggg-report\target\classes;C:\Documents and
> Settings\ge0ffrey\.m2\repository\be\ggg\ggg-api\1.1.3-SNAPSHOT\ggg-api-1.1.3-SNAPSHOT.jar;...
> Notice that it contains spaces, but that shouldn't be a problem as far as I
> know.
> It nicely does
> JRProperties.setProperty( JRProperties.COMPILER_CLASSPATH,
> classpath );
> But apparently jasperreports ignores that parameter:
> http://www.jasperforge.org/sf/go/artf1817
--
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
