[
http://jira.codehaus.org/browse/MPDF-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203188#action_203188
]
Lukas Theussl commented on MPDF-34:
-----------------------------------
Confirmed. MPDF-26 introduced report generation in the pdf, apparently there is
a problem. Unfortunately the default was set to always generate reports (it
should have been optional IMO). You can switch it off as a workaround:
{code:xml}
<configuration>
<includeReports>false</includeReports>
</configuration>
{code}
> plugin fails with AbstractMethodError
> -------------------------------------
>
> Key: MPDF-34
> URL: http://jira.codehaus.org/browse/MPDF-34
> Project: Maven 2.x PDF Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Maven 2.2.1
> Mac OS X
> Reporter: Wendy Smoak
>
> To reproduce, change the pdf plugin version from 1.0 to 1.1 in
> https://svn.apache.org/repos/asf/continuum/trunk/continuum-docs
> With 1.0 it works fine. With 1.1 it fails with:
> $ mvn site -X
> ...
> [FATAL ERROR] org.apache.maven.plugins.pdf.PdfMojo#execute() caused a linkage
> error (java.lang.AbstractMethodError) and may be out-of-date. Check the
> realms:
> [FATAL ERROR] Plugin realm =
> app0.child-container[org.apache.maven.plugins:maven-pdf-plugin:1.1]
> ...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> java.lang.AbstractMethodError
> at
> org.apache.maven.plugins.pdf.PdfMojo.generateMavenReport(PdfMojo.java:1211)
> at
> org.apache.maven.plugins.pdf.PdfMojo.generateMavenReports(PdfMojo.java:1072)
> at org.apache.maven.plugins.pdf.PdfMojo.generatedPdf(PdfMojo.java:545)
> at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:391)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Wed Dec 16 14:25:53 MST 2009
> [INFO] Final Memory: 88M/204M
> [INFO]
> ------------------------------------------------------------------------
>
--
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
