[ 
https://issues.apache.org/jira/browse/DOXIA-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990803#comment-15990803
 ] 
Alex O'Ree commented on DOXIA-492:
----------------------------------

Caused by: java.util.EmptyStackException
        at java.util.Stack.peek(Unknown Source)
        at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)

        at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)

        at org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:87
4)
        at org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBasePar
ser.java:783)
        at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:254)
        at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
        at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
        at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
        at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
        at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractPar
ser.java:136)
        at org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlPar
ser.java:268)
        at org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlPa
rser.java:233)
        at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:263)
        at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
        at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
        at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
        at org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownP
arser.java:112)
        at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
        at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen
t(DefaultSiteRenderer.java:449)
        at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum
ent(DoxiaDocumentRenderer.java:53)
        at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul
tSiteRenderer.java:337)
        at org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(Si
teMojo.java:262)
        at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.j
ava:168)
        at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:1
32)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:134)
        ... 21 more

> Add support for doxia macros in markdown documents.
> ---------------------------------------------------
>
>                 Key: DOXIA-492
>                 URL: https://issues.apache.org/jira/browse/DOXIA-492
>             Project: Maven Doxia
>          Issue Type: Improvement
>          Components: Module - Markdown
>    Affects Versions: 1.4
>            Reporter: Juergen Kellerer
>            Assignee: Hervé Boutemy
>             Fix For: 1.7
>
>         Attachments: maven-site-plugin-integration-test.patch, screen.png
>
>
> It would be nice if doxia macros could be supported also inside markdown 
> documents (similar to APT).
> Existing macros (especially snippet) is very useful, however with the power 
> of maven there's the ability to register own macros for a build process which 
> enables reuse of resources and improves dryness in general.
> A syntax which may work could be the following:
> * Block Level
> {noformat}
>    #`??MACRO_NAME MACRO_ARGS`
> {noformat}
> * Inline
> {noformat}
> `??MACRO_NAME MACRO_ARGS`
> {noformat}
> Reference: 
> http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
> E.g. using "Texts" it works just from the Editor:
> !screen.png!
> When macros are not interpreted, they fallback to a code block, thus it's 
> easy to edit these sort of documents with one of the existing nice markdown 
> editors.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to