You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2024/08/27 18:36:00 UTC
[jira] [Updated] (MJAVADOC-810) [REGRESSION] MJAVADOC-791 causes forked Maven execution fail if any toolchains or settings file isn't present
[ https://issues.apache.org/jira/browse/MJAVADOC-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MJAVADOC-810:
------------------------------------
Summary: [REGRESSION] MJAVADOC-791 causes forked Maven execution fail if any toolchains or settings file isn't present (was: [REGRESSION] MJAVADOC-791 causes forked Maven execution file if any toolchains or settings file isn't present)
> [REGRESSION] MJAVADOC-791 causes forked Maven execution fail if any toolchains or settings file isn't present
> -------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-810
> URL: https://issues.apache.org/jira/browse/MJAVADOC-810
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.8.0, 3.10.0
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.10.1
>
>
> When JavadocUtil invokes another Maven process ({{fork()}}) it passes global/user toolchains/settings file path from {{MavenSession}}. Those values are *always* populated -- if not explciitly provided they will contain the default value, but there is no guarantee that the default value exist. We need to check the value whether it exists and only pass it on if it exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)