[
http://jira.codehaus.org/browse/MOJO-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152997#action_152997
]
Dan Tran commented on MOJO-1254:
--------------------------------
agree, that the problem should not occur. I commit your test case int src/IT.
However, I dont have a solution yet since the build classpath has no traces of
jasperreport 1.2. So what ever throw, must come from jasper 3.1
[DEBUG] buildClasspathString() = G:\dev\mojo\jasperreports-maven-plugin\src\it\M
OJO-1254\target\classes;g:\dev\repository\jasperreports\jasperreports\3.1.0\jasp
erreports-3.1.0.jar;g:\dev\repository\commons-beanutils\commons-beanutils\1.7.0\
commons-beanutils-1.7.0.jar;g:\dev\repository\commons-logging\commons-logging\1.
0.3\commons-logging-1.0.3.jar;g:\dev\repository\commons-collections\commons-coll
ections\2.1\commons-collections-2.1.jar;g:\dev\repository\commons-digester\commo
ns-digester\1.7\commons-digester-1.7.jar;g:\dev\repository\xml-apis\xml-apis\1.3
.02\xml-apis-1.3.02.jar;g:\dev\repository\com\lowagie\itext\2.1.0\itext-2.1.0.ja
r;g:\dev\repository\bouncycastle\bcmail-jdk14\136\bcmail-jdk14-136.jar;g:\dev\re
pository\bouncycastle\bcprov-jdk14\136\bcprov-jdk14-136.jar;g:\dev\repository\jf
ree\jcommon\1.0.12\jcommon-1.0.12.jar;g:\dev\repository\jfree\jfreechart\1.0.9\j
freechart-1.0.9.jar;g:\dev\repository\eclipse\jdtcore\3.1.0\jdtcore-3.1.0.jar
[INFO] Compiling 1 report design files.
[DEBUG] Set classloader
[DEBUG] Added to classpath G:\dev\mojo\jasperreports-maven-plugin\src\it\MOJO-12
54\target\classes
[DEBUG] Added to classpath g:\dev\repository\jasperreports\jasperreports\3.1.0\j
asperreports-3.1.0.jar
[DEBUG] Added to classpath g:\dev\repository\commons-beanutils\commons-beanutils
\1.7.0\commons-beanutils-1.7.0.jar
[DEBUG] Added to classpath g:\dev\repository\commons-logging\commons-logging\1.0
.3\commons-logging-1.0.3.jar
[DEBUG] Added to classpath g:\dev\repository\commons-collections\commons-collect
ions\2.1\commons-collections-2.1.jar
[DEBUG] Added to classpath g:\dev\repository\commons-digester\commons-digester\1
.7\commons-digester-1.7.jar
[DEBUG] Added to classpath g:\dev\repository\xml-apis\xml-apis\1.3.02\xml-apis-1
.3.02.jar
[DEBUG] Added to classpath g:\dev\repository\com\lowagie\itext\2.1.0\itext-2.1.0
.jar
[DEBUG] Added to classpath g:\dev\repository\bouncycastle\bcmail-jdk14\136\bcmai
l-jdk14-136.jar
[DEBUG] Added to classpath g:\dev\repository\bouncycastle\bcprov-jdk14\136\bcpro
v-jdk14-136.jar
[DEBUG] Added to classpath g:\dev\repository\jfree\jcommon\1.0.12\jcommon-1.0.12
.jar
[DEBUG] Added to classpath g:\dev\repository\jfree\jfreechart\1.0.9\jfreechart-1
.0.9.jar
[DEBUG] Added to classpath g:\dev\repository\eclipse\jdtcore\3.1.0\jdtcore-3.1.0
> 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
