[
https://issues.apache.org/jira/browse/DOXIA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906899#comment-15906899
]
Marc Campbell commented on DOXIA-554:
-------------------------------------
[~hboutemy] I will share my thoughts on default for your consideration...
As a long time maven user, I have two broad groups of maven projects: "legacy"
and "new/not-legacy".
The "legacy" projects have expressly stated versions in an appropriate parent
POM. Version updates only occur with specific review of the version change
implications. ("legacy" inheritently has deliberate, cautious version changes)
A "new" projects, as would be created from an IDE template or otherwise, are
expected _to *not* default to something known to be "broken"_. ("new" likes an
automatic default to work with minimal headaches and legacy barriers.)
So, in my use case,
(1) the preferred "default" scenario (which implies "new project") would
_*not* default to a "technical issues" and "un-supported EOL" component_. So,
{{flexmark-java}} would be preferred to {{pegdown}} as the more current default.
_AND_
(2) clear documentation, easy-to-find info needed to management version
selection for conscious legacy versioning. (e.g. main plugin and/or module web
pages. maybe adviory statement(s) in the build output.)
Basically, in my case, "legacy" has expressly mananged versions and "new" is
expected to default conveniently to a non-broken, non-limiting start.
That said, I realize other users (and this Maven Project) may have a different
approaches, priorities and preferences.
> 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)
