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

Olivier Lamy commented on MJAVADOC-785:
---------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-javadoc-plugin#1163|https://github.com/apache/maven-javadoc-plugin/issues/1163].
 

> Align plugin implementation with AbstractMavenReport (maven-reporting-impl)
> ---------------------------------------------------------------------------
>
>                 Key: MJAVADOC-785
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-785
>             Project: Maven Javadoc Plugin (Moved to GitHub Issues)
>          Issue Type: Task
>          Components: javadoc
>    Affects Versions: 3.6.3
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.10.0
>
>
> Due to its complex nature this plugin has never used {{AbstractMavenReport}}, 
> thus not its behavior as well. This causes inconsistencies compared with our 
> other plugins in configuration and runtime behavior. After MSHARED-1327 this 
> plugin will be logically aligned with maven-reporting-impl to mimic the 
> behavior to the extent necessary from {{AbstractMavenReport}}.
> This change the following parameters:
> * {{outputDirectory}} uses the semantics from {{AbstractMavenReport}} and is 
> not exlusive anymore
> * {{destDir}} is gone and folded into {{outputDirectory}}
> * {{reportOutputDirectory}}/{{reportTestOutputDirectory}} is gone and is 
> private according to {{AbstractMavenReport}}, it will be calculated at runtime



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to