[
https://jira.codehaus.org/browse/MOJO-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294510#comment-294510
]
De Moor Yves commented on MOJO-1818:
------------------------------------
Some investigations were done :
Modifications were done in this patch :
http://jira.codehaus.org/browse/MOJO-1141 to solve this kind of issues
For instance creation of this method : private ClassLoader getClassLoader(
ClassLoader classLoader )
And called here Thread.currentThread().setContextClassLoader(
getClassLoader(classLoader) );
This was now removed by this checkin ...
https://fisheye.codehaus.org/browse/mojo/trunk/mojo/jasperreports-maven-plugin/src/main/java/org/codehaus/mojo/jasperreports/JasperReportsMojo.java?r2=16122&r1=8082
Could you please explain why did you removed this ?
> Regression : this fix generates ClassNotFoundException if the jrxml files
> refereces classes under target/classes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MOJO-1818
> URL: https://jira.codehaus.org/browse/MOJO-1818
> Project: Mojo
> Issue Type: Sub-task
> Components: jasperreports
> Environment: plugin version : 1.0-beta-3-SNAPSHOT
> Windows XP
> Java 1.6
> Reporter: De Moor Yves
>
> As explained in the documentation here :
> http://mojo.codehaus.org/jasperreports-maven-plugin/usage.html
> [...] By default, the compile-reports mojo runs at generate-resources phase.
> However, you might need to bind the mojo to the compile phase if your report
> uses classes under target/classes.
> In my module, I have some classes that are compiled under target/classes
> which are referenced from my jrxml file. So I have ser the execution phase
> to compile :
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jasperreports-maven-plugin</artifactId>
> <version>1.0-beta-3-SNAPSHOT</version>
> <configuration>
>
> <sourceDirectory>${basedir}/src/main/resources/jasperreports</sourceDirectory>
>
> <outputDirectory>${project.build.directory}/generated/classes/jasperreports</outputDirectory>
> <source>${jdk.version}</source>
> <target>${jdk.version}</target><!-- JVM version -->
> <debug>true</debug>
> </configuration>
> <executions>
> <execution>
> <phase>process-classes</phase>
> <goals>
> <goal>compile-reports</goal>
> </goals>
> </execution>
> </executions>
> <dependencies>
> <!--note this must be repeated here to pick up correct
> xml validation -->
> <dependency>
> <groupId>net.sf.jasperreports</groupId>
> <artifactId>jasperreports</artifactId>
> <version>${jasperreports.version}</version>
> </dependency>
> </dependencies>
> </plugin>
> This was working right with plugin 1.0-beta2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
