[ 
https://issues.apache.org/jira/browse/DOXIA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895981#comment-15895981
 ] 

Vladimir Schneider commented on DOXIA-554:
------------------------------------------

Someone should tell Travis CI. I tried running a build with JDK6 and got: 
"Sun/Oracle JDK 6 is EOL since November 2012, and is no longer supported. 
Please consider upgrading..."

[https://travis-ci.org/vsch/flexmark-java/builds/207718667|https://travis-ci.org/vsch/flexmark-java/builds/207718667]

I'll wait.

> Parsing time for Markdown documents can take very long and hang site 
> generation
> -------------------------------------------------------------------------------
>
>                 Key: DOXIA-554
>                 URL: https://issues.apache.org/jira/browse/DOXIA-554
>             Project: Maven Doxia
>          Issue Type: Bug
>          Components: Module - Markdown
>    Affects Versions: 1.7
>            Reporter: Michael Benz
>         Attachments: maven-pom-sample-pegdown-performance.zip
>
>
> The parsing time for Markdown documents can take very long and hang site 
> generation when e.g. long tables are being generated.
> The author of pegdown has marked the pegdown project deprecated since 
> 2016-12-14 [pegdown.org|https://github.com/sirthias/pegdown/] and advises to 
> switch to [flexmark-java|https://github.com/vsch/flexmark-java].
> {quote}
> The project is essentially unmaintained with tickets piling up and crucial 
> bugs not being fixed.
> pegdown's parsing performance isn't great. In some cases of pathological 
> input runtime can even become exponential, which means that the parser either 
> appears to "hang" completely or abort processing after a time-out.
> {quote}
> Since the parsing timeout was increased in DOXIA-498 it is now possible to 
> "hang" the site creation with a longer table like the one in this example.
> In case this sample is rendered using version 3.3 of the maven site



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

Reply via email to