You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org> on 2011/10/19 01:49:10 UTC
[jira] [Closed] (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:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1302.
--------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
The tapestry-component-report is gone in 5.3, replaced with a JavaDoc plugin.
> 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
> Assignee: Howard M. Lewis Ship
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira