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

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/07/09 12:31:11 UTC

[jira] [Commented] (MJAVADOC-456) Upgrade to Maven3 plugin

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

Hudson commented on MJAVADOC-456:
---------------------------------

SUCCESS: Integrated in maven-plugins #6862 (See [https://builds.apache.org/job/maven-plugins/6862/])
[MJAVADOC-456] Upgrade to Maven3 plugin
- Remove M2.0 backwards compatible shading
- Reduce number of reports for site-failOnError (also required to run succesfully when invoker.mavenHome points to M3.0) (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1751998])
* maven-javadoc-plugin/pom.xml
* maven-javadoc-plugin/src/it/site-failOnError/pom.xml


> Upgrade to Maven3 plugin
> ------------------------
>
>                 Key: MJAVADOC-456
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-456
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.10.4
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 3.0.0
>
>
> - Upgrade plugin according to https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
> - Remove shading of o.a.m.w.p.ProxyUtils; was done for Maven 2.0.x backwards compatibility



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