Looking forward to seeing a ready-to-use release. I was wondering if we could use sigstore for our Java-based OSS project. But, I had one concern.
Question
I saw that this sigstore-maven plugin expects Java 11. Does the same apply to a target Java project to be released (ex. to Maven Central) with the sigstore-maven plugin?
I know that Java 11 / 17 is getting popular in Java applications. But as far as I know, many OSS Java libraries still choose to stay with Java 8 because they have many dependents. That's the same also for our project.
To use this sigstore-maven plugin for a Java 8 project, will we have to make a complicated configuration to use Java 11 for Maven, and Java 8 for javac?
(Actually we use Gradle, not Maven. But it seems that the same applies because sigstore-java seems Java 11+, too.)
Hi, nice to see the project is ongoing!
Looking forward to seeing a ready-to-use release. I was wondering if we could use sigstore for our Java-based OSS project. But, I had one concern.
Question
I saw that this sigstore-maven plugin expects Java 11. Does the same apply to a target Java project to be released (ex. to Maven Central) with the sigstore-maven plugin?
I know that Java 11 / 17 is getting popular in Java applications. But as far as I know, many OSS Java libraries still choose to stay with Java 8 because they have many dependents. That's the same also for our project.
To use this sigstore-maven plugin for a Java 8 project, will we have to make a complicated configuration to use Java 11 for Maven, and Java 8 for
javac
?(Actually we use Gradle, not Maven. But it seems that the same applies because sigstore-java seems Java 11+, too.)