Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PARQUET-1590: Add Java 11 to Travis #136

Merged
merged 3 commits into from
Jun 17, 2019
Merged

Conversation

Fokko
Copy link
Contributor

@Fokko Fokko commented Jun 3, 2019

.travis.yml Outdated Show resolved Hide resolved
@zivanfi zivanfi changed the title PARQUET-1590: Include JDK11 in the CI PARQUET-1499: Include JDK11 in the CI Jun 11, 2019
@zivanfi zivanfi changed the title PARQUET-1499: Include JDK11 in the CI PARQUET-1590: Add Java 11 to Travis Jun 11, 2019
@zivanfi
Copy link
Contributor

zivanfi commented Jun 12, 2019

Apparently Gradle 4.4.1 does not support Java 11: https://stackoverflow.com/questions/54358107/gradle-could-not-determine-java-version-from-11-0-2

@Fokko
Copy link
Contributor Author

Fokko commented Jun 12, 2019

I'm surprised as well. Thrift is still using Gradle 4.x, while master is at 5.x.

@zivanfi
Copy link
Contributor

zivanfi commented Jun 12, 2019

Travis:

./gradlew wrapper --gradle-version 5.1.1
Downloading https://services.gradle.org/distributions/gradle-4.4.1-bin.zip

That's... interesting...

@Fokko
Copy link
Contributor Author

Fokko commented Jun 12, 2019

Was trying to come up with a workaround, until Thrift 0.13 will be released :-) In the end, right now we're building Thrift 0.12 from scratch, but it should preferred to pull in the binaries instead.

@zivanfi
Copy link
Contributor

zivanfi commented Jun 12, 2019

I'm officially confused:

zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.1.1
Downloading https://services.gradle.org/distributions/gradle-4.4.1-bin.zip

zi@kermit:/tmp (0)$ ./gradlew wrapper --distributionUrl=https\://services.gradle.org/distributions/gradle-5.4.1-bin.zip
Downloading https://services.gradle.org/distributions/gradle-5.1.1-bin.zip

Since the --gradle-version parameter seemed to have no effect, I have tried the --distributionUrl parameter using an example from the Gradle docs. I requested version 5.4.1 and got 5.1.1... But why?

@Fokko
Copy link
Contributor Author

Fokko commented Jun 12, 2019

That feels weird indeed. I think the explanation is somewhere here: https://docs.gradle.org/current/userguide/gradle_wrapper.html#customizing_wrapper

With the configuration in place running ./gradlew wrapper --gradle-version 5.4.1 is enough to produce a distributionUrl value in the Wrapper properties file that will request the -all distribution.

I think the distributionUrl is being overridden by the earlier -gradle-version 5.1.1.

@zivanfi
Copy link
Contributor

zivanfi commented Jun 12, 2019

It just keeps getting better and better:

zi@kermit:/tmp (0)$ rm -r ~/.gradle
zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.4.1
Downloading https://services.gradle.org/distributions/gradle-5.4.1-bin.zip
zi@kermit:/tmp (0)$ rm -r ~/.gradle
zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.1.1
Downloading https://services.gradle.org/distributions/gradle-5.4.1-bin.zip

@zivanfi
Copy link
Contributor

zivanfi commented Jun 12, 2019

I think I solved the mystery. From a clean state:

zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.1.1
Downloading https://services.gradle.org/distributions/gradle-4.4.1-bin.zip
zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.1.1
Downloading https://services.gradle.org/distributions/gradle-5.1.1-bin.zip
zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.4.1
# Nothing downloaded
zi@kermit:/tmp (0)$ ./gradlew wrapper --gradle-version 5.4.1
Downloading https://services.gradle.org/distributions/gradle-5.4.1-bin.zip

It seems to me that these options only have an effect of the next command, but not the current one. They set the URL that is located in the ./wrapper/gradle-wrapper.properties file, but only after the gradle wrapper has already read them, therefore it will keep using the old values until restarted.

@Fokko
Copy link
Contributor Author

Fokko commented Jun 12, 2019

@zivanfi This makes perfect sense. Also in the CI, we see that it first runs the current version, and then it tries to upgrade/set the new version.

@zivanfi
Copy link
Contributor

zivanfi commented Jun 14, 2019

Do you see any way to make this work?

@Fokko
Copy link
Contributor Author

Fokko commented Jun 14, 2019

Yes, I found a way. We don't need to compile the Java stuff actually, because maven will just pull this from maven central. Therefore we don't need gradle :-)

@zivanfi zivanfi merged commit 4157b4c into apache:master Jun 17, 2019
@Fokko Fokko deleted the PARQUET-1590 branch June 17, 2019 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants