-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Jdk8 variant of this plugin? #6
Comments
I tried to find a solution to this issue (except downgrading dependencies), but I found none. |
Just a wild guess (haven't tried it etc.) but maybe you could define JVM toolchain? https://docs.gradle.org/current/userguide/toolchains.html |
@pmendelski This PR may help: #8 |
@kkocel Many thanks for the very first external contribution to this project 🎉 I've just released the plugin under |
I checked it with the axion plugin and it works. Why it's working? It turns out that Gradle started to publish Inside pom file you can read: <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- This module was also published with a richer model, Gradle metadata, -->
<!-- which should be used instead. Do not delete the following line which -->
<!-- is to indicate to Gradle or any Gradle module metadata file consumer -->
<!-- that they should prefer consuming it instead. -->
<!-- do_not_remove: published-with-gradle-metadata -->
"org.gradle.jvm.version": 11, So defining explicit version in the JVM toolchain and updating GitHub workflow did the trick :) |
Recently I tried to use the newest version of
gradle-integration-test-plugin
and it failed since the project where I applied it had jdk8.I got the following error message:
Logs can be found here:
https://github.com/allegro/axion-release-plugin/runs/3008018485
Is there a possibility to make this library jdk8 compatible?
The text was updated successfully, but these errors were encountered: