-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 with jdk14 and gradle 6.3 #2088
Conversation
Codecov Report
@@ Coverage Diff @@
## 3.2.x #2088 +/- ##
============================================
- Coverage 84.78% 84.61% -0.18%
+ Complexity 3983 3977 -6
============================================
Files 364 364
Lines 30271 30267 -4
Branches 5615 5607 -8
============================================
- Hits 25666 25609 -57
- Misses 3000 3042 +42
- Partials 1605 1616 +11
Continue to review full report at Codecov.
|
- Bump Kotlin plugin to 1.3.71 - Remove osgi plugin and replace with BND - Add explicit jar task to reactor-test to apply bnd - Improve BND import/export configuration - Bump jacoco to 0.8.5 for minimal JDK 14 compatibility
66b17f5
to
fc80479
Compare
Note that the BND manifest output was compared to old osgi output, with the following caveats:
|
- Bump Kotlin plugin to 1.3.71 - Remove osgi plugin and replace with BND - Add explicit jar task to reactor-test to apply bnd - Improve BND import/export configuration - Bump jacoco to 0.8.5 for minimal JDK 14 compatibility
@simonbasle this PR seems to have been merged on a maintenance branch, please ensure the change is merge-forwarded to intermediate maintenance branches and up to |
- OSGI helper is also removed from buildSrc - BND configuration is updated to add blockhound
- build-scan plugin (added in 3.3) has been upgraded but must now be applied in settings.gradle - unbroken-dome.test-sets plugin must be bumped to version 3.0.0 for Gradle 6.3 compatibility - core BND export-package gets confused by 3.3.x "java9stubs", so we get more explicit about the packages we export (one level of detail beyond `reactor.*`)
- build-scan plugin (added in 3.3) has been upgraded but must now be applied in settings.gradle - unbroken-dome.test-sets plugin must be bumped to version 3.0.0 for Gradle 6.3 compatibility - Bump of blockhound to 1.0.3 to avoid `reactor.shaded` version of bytebuddy (which confuses BND) - Exclude blockhound in core's BDN Export-Package
- build-scan plugin (added in 3.3) has been upgraded but must now be applied in settings.gradle - unbroken-dome.test-sets plugin must be bumped to version 3.0.0 for Gradle 6.3 compatibility - Bump of blockhound to 1.0.3 to avoid `reactor.shaded` version of bytebuddy (which confuses BND) - Exclude blockhound in core's BDN Export-Package
The specifics include: - build-scan plugin (added in 3.3) has been upgraded but must now be applied in settings.gradle - unbroken-dome.test-sets plugin must be bumped to version 3.0.0 for Gradle 6.3 compatibility - Bump of blockhound to 1.0.3 to avoid `reactor.shaded` version of bytebuddy (which confuses BND) - Exclude blockhound in core's BDN Export-Package - fix a flakky GC test
In #2088 a refactoring relocated OSGi metadata generation from the base build file to the respective modules. There was a mistake during that transition where the javax.annotation.meta was missed in the exclusions of the reactor-core bundle. Co-authored-by: gurkerl83 <markus_gritsch@gmx.de>
No description provided.