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

Daniel Gazineu updated BEAM-7931:
---------------------------------
    Comment: was deleted

(was: This is an issue with the way Gradle Wrapper works 
[https://github.com/gradle/gradle/issues/4463]. 

A stopgap solution is to manually override distributionUrl on 
gradle/wrapper/gradle-wrapper.properties. You can replace it with a URL within 
your corporate network or even a file in your filesystem. i.e:


{code:java}
sed -i 
's/https\\:\/\/services.gradle.org\/distributions/file\\:\/\/\/home\/username\/gradle-cache/g'
 gradle/wrapper/gradle-wrapper.properties
{code}
 )

> Fix gradlew to allow offline builds
> -----------------------------------
>
>                 Key: BEAM-7931
>                 URL: https://issues.apache.org/jira/browse/BEAM-7931
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Chad Dombrova
>            Priority: Major
>
> When running `./gradlew` the first thing it tries to do is download gradle:
> {noformat}
> Downloading https://services.gradle.org/distributions/gradle-5.2.1-all.zip
> {noformat}
> There seems to be no way to skip this, even if the correct version of gradle 
> has already been downloaded and exists in the correct place.  The tool should 
> be smart enough to do a version check and skip downloading if it exists.  
> Unfortunately, the logic is wrapped up inside 
> gradle/wrapper/gradle-wrapper.jar so there does not seem to be any way to fix 
> this.  Where is the code for this jar?
> This is the first step of several to allow beam to be built offline.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to