You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Antal van Kalleveen (JIRA)" <ji...@apache.org> on 2011/01/07 09:39:46 UTC
[jira] Commented: (TAP5-1302) tapestry-component-report fails due
to doxia dependency error
[ https://issues.apache.org/jira/browse/TAP5-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978681#action_12978681 ]
Antal van Kalleveen commented on TAP5-1302:
-------------------------------------------
I'm having the same issue, updating the site plugin to version 2.0-beta-5 did not resolve the problem. Here is an excerpt of my plugin dependencies:
[INFO] Plugin Resolved: tapestry-component-report-5.2.4.jar
[INFO] Plugin Dependency Resolved: maven-project-2.0.9.jar
[INFO] Plugin Dependency Resolved: maven-plugin-api-2.0.9.jar
[INFO] Plugin Dependency Resolved: plexus-utils-1.5.6.jar
[INFO] Plugin Dependency Resolved: maven-plugin-descriptor-2.0.9.jar
[INFO] Plugin Dependency Resolved: maven-reporting-impl-2.0.4.1.jar
[INFO] Plugin Dependency Resolved: doxia-site-renderer-1.0-alpha-11.jar
[INFO] Plugin Dependency Resolved: commons-lang-2.1.jar
[INFO] Plugin Dependency Resolved: tapestry-ioc-5.2.4.jar
[INFO] Plugin Dependency Resolved: xom-1.1.jar
[INFO] Plugin Dependency Resolved: tools.jar
[INFO] Plugin Resolved: maven-clean-plugin-2.4.1.jar
[INFO] Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar
[INFO] Plugin Dependency Resolved: plexus-utils-2.0.5.jar
[INFO] Plugin Resolved: maven-surefire-plugin-2.5.jar
[INFO] Plugin Dependency Resolved: maven-plugin-api-2.0.9.jar
[INFO] Plugin Dependency Resolved: surefire-booter-2.5.jar
[INFO] Plugin Dependency Resolved: plexus-utils-1.5.9.jar
[INFO] Plugin Dependency Resolved: maven-artifact-2.0.9.jar
[INFO] Plugin Dependency Resolved: maven-project-2.0.9.jar
[INFO] Plugin Dependency Resolved: maven-core-2.0.9.jar
[INFO] Plugin Dependency Resolved: maven-toolchain-2.0.9.jar
[INFO] Plugin Resolved: maven-site-plugin-2.0-beta-5.jar
[INFO] Plugin Dependency Resolved: maven-plugin-api-2.0.jar
[INFO] Plugin Dependency Resolved: maven-artifact-2.0.2.jar
[INFO] Plugin Dependency Resolved: maven-project-2.0.jar
[INFO] Plugin Dependency Resolved: maven-settings-2.0.jar
[INFO] Plugin Dependency Resolved: doxia-site-renderer-1.0-alpha-8.jar
[INFO] Plugin Dependency Resolved: maven-reporting-api-2.0.2.jar
[INFO] Plugin Dependency Resolved: plexus-utils-1.1.jar
[INFO] Plugin Dependency Resolved: jetty-6.0.0beta12.jar
> tapestry-component-report fails due to doxia dependency error
> -------------------------------------------------------------
>
> Key: TAP5-1302
> URL: https://issues.apache.org/jira/browse/TAP5-1302
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-component-report
> Affects Versions: 5.2.0, 5.1.0.5
> Reporter: Inge
> Priority: Critical
>
> First of all, I encountered this bug, which prevents component report to run on Windows 7:
> https://issues.apache.org/jira/browse/TAP5-871
> After applying the patch found in that issue, I ran into the next one:
> java.lang.NoSuchMethodError: org.apache.maven.doxia.module.xhtml.XhtmlSink.writeEndTagWithoutEOL(Ljavax/swing/text/html/HTML$Tag;)V
> at org.apache.maven.doxia.module.xhtml.XhtmlSink.link_(XhtmlSink.java:1066)
> at org.apache.tapestry.mojo.ComponentReport.executeReport(ComponentReport.java:240)
> at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
> at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:65)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:345)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:132)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:290)
> 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:592)
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.