[ 
https://issues.apache.org/jira/browse/MJAVADOC-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MJAVADOC-791.
-----------------------------------
    Resolution: Fixed

Fixed with 
[3eb47c5081bf6f4158333bd378641bc9b7c9a25f|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=3eb47c5081bf6f4158333bd378641bc9b7c9a25f].

> maven-javadoc-plugin not working correctly together with 
> maven-toolchains-plugin
> --------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-791
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-791
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 3.6.3
>            Reporter: Hristo Bozhilov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.7.1
>
>
> We are using maven-javadoc-plugin in conjunction with maven-toolchains-plugin 
> and we are facing an unpleasant problem.
> We have defined toolchains.xml file containing jdk versions needed for the 
> build.
> For our build automation server we are using jenkins Config File Provider 
> plug-in to supply this toolchains.xml file to the build via -t command line 
> argument e.g:
> {code:java}
> mvn clean deploy -t <path generated by the Config File Provider 
> plug-in>.{code}
> We have maven multi-module build and some modules use maven-javadoc-plugin to 
> generate javadocs for our API. Sometimes we have API modules that refer API 
> classes located in another API module. maven-javadoc-plugin tries to link all 
> of these but it fails every time with this error: "[ERROR] No toolchain found 
> for type jdk".
> I've looked to the source repository of maven-javadoc-plugin on github and I 
> noticed that it forks maven process to build dependent javadocs without 
> passing info from toolchains.xml to the forked maven which is needed to run 
> the javadoc build. Instead the forked process always expects that 
> toolchains.xml is located to ~/.m2/toolchains.xml and this doesn't work on 
> jenkins.
>  



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

Reply via email to