DTD validation broken for jasperreports versions later than 1.2
---------------------------------------------------------------
Key: MOJO-1254
URL: http://jira.codehaus.org/browse/MOJO-1254
Project: Mojo
Issue Type: Bug
Components: jasperreports
Environment: Linux x86, maven 2.0.9
Reporter: Pete Gillis
Priority: Critical
Attachments: JasperPlugintest.zip
Apparently this plugin depends on jasperreport 1.2. This is fine unless you are
using new attributes that are not in that version of the DTD. One work around
would be to turn off validation, not acceptable.
The other work around is to add a dependency on the plugin for the version of
jasperreports you are using. This will throw the correct DTD in the classpath
ahead of the 1.2 verison, and will allow validation to work. The downside, this
may break if there are binary incompatibilities with 1.2.
Perhaps another configuration option to set jasperreports version?
I am attaching a zipped up maven project that illustrates the problem.
--
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
