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

[build] bump gradle to latest 5.x release #1923

Conversation

grimreaper
Copy link
Contributor

Problem

Gradle is out date which results in us not having bugs fixed, new
features, or performance improvements

Solution

Upgrade gradle to the latest 5.x (current major version we use). Also
switch from -bin to -all which mildly increases distribution size
but makes it much easier to debug or diagnose issues. This has no impact
to end users.

  • Read the contributing guide
  • PR should be motivated, i.e. what does it fix, why, and if relevant how
  • If possible / relevant include an example in the description, that could help all readers
    including project members to get a better picture of the change
  • Avoid other runtime dependencies
  • Meaningful commit history ; intention is important please rebase your commit history so that each
    commit is meaningful and help the people that will explore a change in 2 years
  • The pull request follows coding style
  • Mention Fixes #<issue number> in the description if relevant
  • At least one commit should mention Fixes #<issue number> if relevant

Problem

Gradle is out date which results in us not having bugs fixed, new
features, or performance improvements

Solution

Upgrade gradle to the latest 5.x (current major version we use). Also
switch from `-bin` to `-all` which mildly increases distribution size
but makes it much easier to debug or diagnose issues. This has no impact
to end users.
@grimreaper grimreaper force-pushed the eax/gw/bump-gradle-to-latest-5 branch from 4584d40 to 5c6356a Compare May 4, 2020 03:58
TimvdLippe added a commit that referenced this pull request Jun 15, 2020
This included a couple of breaking changes:
- The build plugin is now part of the Gradle Enterprise plugin
- The osgi plugin was removed, for which we have to use the bndtools
plugin instead
- Kotlin version has to be updated, including their coroutine
library versions

Gradle 6 is required for us to build on Java 14.

Supersedes and closes #1923
@TimvdLippe TimvdLippe mentioned this pull request Jun 15, 2020
TimvdLippe added a commit that referenced this pull request Jun 16, 2020
* Upgrade to Gradle 6

This included a couple of breaking changes:
- The build plugin is now part of the Gradle Enterprise plugin
- The osgi plugin was removed, for which we have to use the bndtools
plugin instead
- Kotlin version has to be updated, including their coroutine
library versions

Gradle 6 is required for us to build on Java 14.

Supersedes and closes #1923

* Remove commented plugin

* Move checksum computation out of Gradle

Gradle 6 does not like that we run a build twice, as part of a Gradle
task. Therefore, we have to move the checksum computation out of
the gradle task in a separate Bash script.

* Run reproducibility check as a separate Travis build

Otherwise we lose the code coverage, as we run a `gradle clean`
in the reproducibility check.

* Fix code coverage

This now also makes use of the build cache, which should significantly
speed up Travis builds.

* Fix disabling of projects for the coverage task

* Fix exclusion of errorprone subproject

* Reverse logic in coverage.gradle
epeee pushed a commit to epeee/mockito that referenced this pull request Jun 22, 2020
* Upgrade to Gradle 6

This included a couple of breaking changes:
- The build plugin is now part of the Gradle Enterprise plugin
- The osgi plugin was removed, for which we have to use the bndtools
plugin instead
- Kotlin version has to be updated, including their coroutine
library versions

Gradle 6 is required for us to build on Java 14.

Supersedes and closes mockito#1923

* Remove commented plugin

* Move checksum computation out of Gradle

Gradle 6 does not like that we run a build twice, as part of a Gradle
task. Therefore, we have to move the checksum computation out of
the gradle task in a separate Bash script.

* Run reproducibility check as a separate Travis build

Otherwise we lose the code coverage, as we run a `gradle clean`
in the reproducibility check.

* Fix code coverage

This now also makes use of the build cache, which should significantly
speed up Travis builds.

* Fix disabling of projects for the coverage task

* Fix exclusion of errorprone subproject

* Reverse logic in coverage.gradle
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

1 participant