Failed to use 1.1.0-RC with maven and just release repositories
See original GitHub issueDescribe the bug
To Reproduce We put the following dependency on our project:
<dependency>
<groupId>org.jetbrains.kotlinx</groupId>
<artifactId>kotlinx-serialization-json</artifactId>
<version>1.1.0-RC</version>
</dependency>
The following error is popping up:
[ERROR] Failed to execute goal on project web-api: Could not resolve dependencies for project co.c.prod.jp:web-api:jar:kotlinSerialization-000101: Failed to collect dependencies at org.jetbrains.kotlinx:kotlinx-serialization-json:jar:1.1.0-RC -> org.jetbrains.kotlinx:kotlinx-serialization-json-jvm:jar:1.1.0-RC -> org.jetbrains.kotlin:kotlin-stdlib:jar:1.4.30-270: Failed to read artifact descriptor for org.jetbrains.kotlin:kotlin-stdlib:jar:1.4.30-270: Could not transfer artifact org.jetbrains.kotlin:kotlin-stdlib:pom:1.4.30-270 from/to central-maven (http://repo1.maven.org/maven2): Transfer failed for http://repo1.maven.org/maven2/org/jetbrains/kotlin/kotlin-stdlib/1.4.30-270/kotlin-stdlib-1.4.30-270.pom 501 HTTPS Required -> [Help 1]
It seems that 1.1.0-RC
is declaring a dependency on the stdlib version 1.4.30-270
, which is not available on repo1.
Expected behavior Maven project should build with no issues.
Environment
- Kotlin version: 1.4.30
- Library version: 1.1.0-RC
- Kotlin platforms: JVM
- Maven version: 3.6.3
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:8
Top Results From Across the Web
Maven Could not resolve dependencies, artifacts could not be ...
The artifactId for all the dependencies that failed to download are incorrect ... <repository> <id>org.springframework.maven.release</id> <name>Spring Maven ...
Read more >Maven Getting Started Guide
How do I compile my test sources and run my unit tests? ... is released as version 1.0, and the new development version...
Read more >org.codehaus.groovy - Maven Repository
License, Apache 2.0. Categories, JVM Languages. Tags, jvmlanguagegroovycodehaus. Ranking, #98 in MvnRepository (See Top Artifacts) #5 in JVM Languages.
Read more >Maven Central Repository Search
Official search by the maintainers of Maven Central Repository. ... Introducing the new look of The Central Repository, designed to address artifact search ......
Read more >Maven Error: Failed to collect dependencies - When trying to ...
Check the release notes if you really want to use 3.8.4 jars only then raise a ticket with MuleSoft. Else go to the...
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 FreeTop 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
Top GitHub Comments
I excluded kotlin-stdlib and kotlin-stdlib-common, that force to use kotlin 1.4.30
Indeed it seems so, I removed the exclusions and there do not appear to be any errors in the Maven project. The dependencies now point to Kotlin 1.4.30 final versions.
However, I think it’s something for JetBrains to pay attention to for the next RC release that is published to Maven Central.