Hi Felipe, This is fixed in version 1.0-beta-1 of the plugin. You must add the dependency of your vc-entities as dependency to the plugin, too (like the jasperreports dependency). This should solve your problem. Cheers, Andi
________________________________ From: Felipe Cypriano [mailto:[email protected]] Sent: Freitag, 10. Juli 2009 15:21 To: [email protected] Subject: [mojo-user] Re: JasperReports plugin not compiling when classes are from pom.xml (MOJO-1141) I've looked in svn of jasperreports plugin and the patch provided by MOJO-1141 <http://jira.codehaus.org/browse/MOJO-1141> is there, but how do I know if the version that I'm using is fixed? FYI, I started using jasperreports plugin yesterday. Regards, --- Felipe Cypriano On Thu, Jul 9, 2009 at 15:11, Felipe Cypriano <[email protected]> wrote: Hello, I've just post a comment in MOJO-1141 <http://jira.codehaus.org/browse/MOJO-1141> , but maybe here is a better place to ask, so this is the problem: I'm having problems with classpath and pom dependencies. I get this errors: Error compiling report design : D:\Projetos\Java\vc-web\vc-grails\src\main\jasperreports\PedidoVendaResu mo.jrxml : Report design not valid : 1. java.lang.ClassNotFoundException: vc.entity.Transportadora 2. java.lang.ClassNotFoundException: vc.commons.OrigemEstoque 3. java.lang.ClassNotFoundException: entity.CondicaoPagamento All theses classes are pom dependencies: <!-- omitted code --> <dependency> <groupId>br.com.litoraltextil.vc</groupId> <artifactId>vc-entities</artifactId> <version>2.0-SNAPSHOT</version> </dependency> <!-- omitted code --> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jasperreports-maven-plugin</artifactId> <executions> <execution> <goals> <goal>compile-reports</goal> </goals> </execution> </executions> <dependencies> <!--note this must be repeated here to pick up correct xml validation --> <dependency> <groupId>jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>${jasperreports.version}</version> </dependency> </dependencies> </plugin> <!-- omitted code --> Is the fix already released? How could I fix this problem? --- Felipe Cypriano
