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
JitPack fails building Pioneer: "invalid flag: -Xlint:all,-exports" #677
Comments
But why our builds are green then? |
The lowest Java version we use in our build is 11, but we target Java 8 (i.e. bytecode version 52.0): https://github.com/junit-pioneer/junit-pioneer/blob/main/build.gradle.kts#L30 However, there are parts of the Gradle script that can only be built with JDK 11+, e.g.: https://github.com/junit-pioneer/junit-pioneer/blob/main/build.gradle.kts#L227 JitPack doesn't know that:
https://jitpack.io/docs/BUILDING/#java-version Therefore, I think we can sidestep this issue by creating a |
But why do we care, as we build with GitHub Actions? |
JitPack allows user to use unpublished (in terms of Maven Central) Pioneer versions, such as a specific branch or commit, without checking out the project and building it locally. In the past, we were trying to make JitPack work, too (e.g. #482). |
From the [JitPack docs](https://jitpack.io/docs/BUILDING/#java-version): >JitPack will compile projects using OpenJDK Java 8. See the example >projects on how to set a different target version in your build file. > >Maven projects that specify a target version in their pom will be >built with that target version. > >If your project uses Travis or Circle CI then JitPack will read the >lowest jdk version from yml file and use that to build. > >Alternatively create a jitpack.yml file in the root of your >repository and specify a jdk version: This PR adds a `jitpack.yml`, specifying OpenJDK 11 to be used. Closes: #677 PR: #678
@beatngu13 Should we not configure JitPack to run the modular build? |
JitPack fails building Pioneer (v1.7.1), from the build log:
I assume this is because we are building with 11 (targeting 8), whereas JitPack is using 8, which doesn't know the
Xlint
keyexports
.The text was updated successfully, but these errors were encountered: