[MSITE-105] No line number for Doxia barfs makes using APT to write site documentation all but impossible

• Type: New Feature
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0-beta-4
• Fix Version/s: 2.0-beta-5
• Environment: all
• Assignee: Jesse Stockall
• Reporter: Greg Luck
• Created: 15/Mar/06 23:40
• Updated: 06/Apr/06 15:36
• Resolved: 01/Apr/06 23:52

Description

The following is a typical error message complaining about the lack of a closing > tag. Also happens regularly with missing } tags when you are doing links. Getting a message like that in a 1000 line document is impossible to debug.

It should specify the line number. and ideally the column number.

[ERROR] Error rendering /Users/gluck/work/ehcache/src/site/apt/documentation/logging.apt: missing '>'
org.codehaus.doxia.module.apt.AptParseException: missing '>'
at org.codehaus.doxia.module.apt.AptParser.doTraverseText(AptParser.java:1011)
at org.codehaus.doxia.module.apt.AptParser.access$500(AptParser.java:27)
at org.codehaus.doxia.module.apt.AptParser$Block.traverseText(AptParser.java:1211)
at org.codehaus.doxia.module.apt.AptParser$Block.traverseText(AptParser.java:1206)
at org.codehaus.doxia.module.apt.AptParser$Paragraph.traverse(AptParser.java:1484)
at org.codehaus.doxia.module.apt.AptParser.traverseSectionBlocks(AptParser.java:238)
at org.codehaus.doxia.module.apt.AptParser.traverseBody(AptParser.java:148)
at org.codehaus.doxia.module.apt.AptParser.parse(AptParser.java:110)
at org.codehaus.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:221)
at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:173)
at org.codehaus.plexus.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:152)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:340)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
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:585)
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)

Try parsing the following snippet to get the above error:

------------------------------------------
<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"

properties="peerDiscovery=manual,
rmiUrls=//server2:40001/sampleCache11|//server2:40001/sampleCache12"/>
------------------------------------------