I would suggest running maven with the -X switch and piping the output to a log file. The plugin should print its classpath to the log. e.g. on Windows:
mvn -X compile > mvn.log You can then check the classpath used by the maven plugin. Another thing to check is that the plugin uses the same version of JasperReports that you have listed as a dependency - you may want to try adding the dependency on JasperReports to the plugin configuration as well and see if that helps. Mike On 8/30/07, Jesfre <[EMAIL PROTECTED]> wrote: > > > But tha packages are in the .m2 repository, however, maven tells that the > packages doesn't exist. > Is so weird. :S > > > mraible wrote: > > > > I'd suggest asking this on the JasperReports forum. Does it work in > > your IDE? If so, then it's probably a Maven problem. Maybe the package > > names changed? > > > > Matt > > > > On 8/30/07, Jesfre <[EMAIL PROTECTED]> wrote: > > > > -- > > http://raibledesigns.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Jasperreports-compilation-error%21-tf4350546s2369.html#a12411176 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
