[GRADLE-1228] When building Gradle javadoc creation doesn't inherit proxy settings Created: 21/Nov/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Bug
Reporter: John Gibson Assignee: Unassigned
Resolution: Won't Fix Votes: 4


The javadoc portion of the Gradle build doesn't inherit the proxy settings when they are specified via GRADLE_OPTS. This doesn't fail the build but delays it significantly while waiting for network timeouts. In addition the final javadoc doesn't have proper links to the external websites.

I imagine that this problem occurs because the Javadoc ant task doesn't inherit proxy settings from the environment:

Comment by Thomas Jensen [ 29/Oct/14 ]

There is a workaround that may be helpful until the issue gets fixed. In your build script, use the jFlags option to transfer the proxy settings to the javadoc task:

javadoc {
    options.jFlags('-DproxyHost=' + System.properties['http.proxyHost'],
            '-DproxyPort=' + System.properties['http.proxyPort'],
            '-DproxyUser=' + System.properties['http.proxyUser'],
            '-DproxyPassword=' + System.properties['http.proxyPassword']);

This assumes that you have specified the proxy settings in your gradle.properties like this:


proxyUser and proxyPassword can be omitted if the proxy does not require authentication.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:50:14 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.