You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2015/08/31 00:15:45 UTC

[jira] [Closed] (MPDF-62) PDF plugin doesn't work with doxia-module-markdown

     [ https://issues.apache.org/jira/browse/MPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy closed MPDF-62.
-----------------------------
       Resolution: Fixed
         Assignee: Hervé Boutemy
    Fix Version/s: 1.4

fixed in [r1700169|http://svn.apache.org/r1700169]: Markdown parser was not in dependency list

you don't need to wait for the release to benefit from Markdown: you just need to add the dependency to the maven-pdf-plugin when using it

> PDF plugin doesn't work with doxia-module-markdown
> --------------------------------------------------
>
>                 Key: MPDF-62
>                 URL: https://issues.apache.org/jira/browse/MPDF-62
>             Project: Maven PDF Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Fabio Napoleoni
>            Assignee: Hervé Boutemy
>             Fix For: 1.4
>
>
> I have a maven 3 project which uses doxia-module-markdown for generating maven site. While the site is generated with no issues if I try to generate pdf version of the site using maven-pdf-plugin the resulting pdf has only TOC entries for markdown documents while working fine with apt ones.
> Here is an excerpt of my pdf.xml file:
> {code:xml}
>     <toc name="Table of Contents">
>         <item name="Introduction" ref="intro.apt"/>
>         <item name="Usage" ref="index.md"/>
>         <item name="Authentication" ref="auth.md"/>
>     </toc>
> {code}
> The intro ref is an apt document I've added to test the issue, and it is rendered in the final pdf, while the other two documents which are couple of markdown files included in site generation are not rendered in the final pdf while they have their TOC entries.
> Is there any workaround to this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)