You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/11/24 11:50:00 UTC

[jira] [Commented] (MJAVADOC-510) Investigate JavadocUtil.invokeMaven

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

Robert Scholte commented on MJAVADOC-510:
-----------------------------------------

Might be interesting to switch to [https://revapi.org/] since Clirr is quite dead.

> Investigate JavadocUtil.invokeMaven
> -----------------------------------
>
>                 Key: MJAVADOC-510
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-510
>             Project: Maven Javadoc Plugin
>          Issue Type: Task
>            Reporter: Stephen Connolly
>            Priority: Major
>             Fix For: 3.0.2
>
>
> Spotted while fine-tuning the Jenkinsfile builds. Unclear why Javadoc plugin needs to fork Maven and whether it is doing it the correct way if the requirement is actually valid.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)