Version 0.1.45 on Maven Central requires JDK 11
See original GitHub issueSimilar to this other issue, the latest release of 0.1.45 in Maven Central requires Java11 in its Gradle module file.
This wasn’t an issue in the jcenter publication because it was published with a previous version of Gradle and did not include a .module
file.
This will make build fail in setups were Maven Central has a higher precedence than Jcenter and using Java8.
2 possible solutions:
- removing the .module file from Maven Central, not sure how possible this is
- publishing a patched 0.1.46 version that declares Java8 compatibility (see https://github.com/square/kotlinpoet/pull/1000). It looks like
markdown
is included transitively bydokka
so users would have to explicitely upgrademarkdown
but that gives a path forward
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Maven Could not resolve dependencies, artifacts could not be ...
I've tried downloading the newest version of maven, and included it in the eclipse helios, but still the same problem. The same error...
Read more >Migrate Maven Projects to Java 11 - winterbe
Learn how to migrate Maven projects from Java 8 to 11 (Jigsaw Module System)
Read more >JSch - com.jcraft - Maven Repository
JSch is a pure Java implementation of SSH2 ... Version, Vulnerabilities, Repository, Usages, Date ... Oct 11, 2012. 0.1.48 · 1 vulnerability ·...
Read more >Getting Started With Gradle: Dependency Management
If we want to add a Maven repository by using its url, we have to add the following code snippet to the build.gradle...
Read more >Maven Central Repository Search
Official search by the maintainers of Maven Central Repository.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
forcing the newer version resolved things for us 👍. Thanks for the quick turnaround on this!
Joel has removed the
.module
file from faulty 0.1.45 release so builds should be fine again (after cleaning local module caches fororg.jetbrains:markdown:0.1.45
, if present). Please ping me if something still does not work.