[
https://issues.apache.org/jira/browse/MJAVADOC-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763229#comment-17763229
]
Henning Schmiedehausen commented on MJAVADOC-642:
-------------------------------------------------
The explanation above is wrong.
The "isOffline" setting is controlled by "${settings.offline}", which is part
of the maven internal settings. It can not be controlled by
{{-Dsettings.offline=true}} but by passing the {{-o}} parameter to maven.
Neither setting maven.javadoc.isOffline nor setting settings.offline on the
command line has any effect.
Currently, the only way to run the javadoc plugin in offline mode is to pass
the {{-o}} flag to maven itself. I will add a property setting in a PR and
then close this issue as fixed.
> Setting maven.javadoc.isoffline seems to have no effect
> -------------------------------------------------------
>
> Key: MJAVADOC-642
> URL: https://issues.apache.org/jira/browse/MJAVADOC-642
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
> Affects Versions: 3.1.1
> Reporter: Thomas Cunningham
> Priority: Major
> Fix For: wontfix-candidate, waiting-for-feedback
>
>
> I'm trying to work around MJAVADOC-641 and the proxy issues that we are
> having, and I'd like to set isOffline to true. I tried to do this my
> setting -Dmaven.javadoc.isOffline=true in my maven invocation, and it doesn't
> seem to take effect. Setting isOffline to true within the <configuration/>
> allows my build to succeed.
> Am I using the wrong command line property for isOffline?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
