https://linen.dev logo
Powered by
#help
Title
p

Przemek Bielicki

09/01/2023, 8:38 AM
Hey folks 👋 I’m having troubles getting the latest release from Maven Central:
Copy code
> Could not find org.wiremock:wiremock-jre8:3.0.0.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/org/wiremock/wiremock-jre8/3.0.0/wiremock-jre8-3.0.0.pom>
https://scans.gradle.com/s/ggblm73itocgo/failure#1 🧵
As I can see in the https://repo.maven.apache.org/maven2/com/github/tomakehurst/wiremock-jre8/ it’s a little disorder. Version 3.0.1 is missing and https://repo.maven.apache.org/maven2/org/wiremock/ is missing 
wiremock-jre8
completely.
Should I use different Maven repository? Can you please document it?
Steps to reproduce below. 
build.gradle.kts
:
Copy code
plugins {
    java
}

repositories {
    mavenCentral()
}

dependencies {
    implementation("com.github.tomakehurst:wiremock-jre8:3.0.0")
}
+ empty Java class file inside 
/src/main/java
and then run 
./gradlew build
l

Lee Turner

09/01/2023, 8:48 AM
Hi 👋 One of the key changes for wiremock 3 was including support for java 17 and dropping java 8 support - https://github.com/wiremock/wiremock/releases/tag/3.0.0
Breaking changes - Java 8 is no longer supported, WireMock will NOT work on this version anymore
That is perhaps why the 
jre8
artifact isn’t there for version 3
p

Przemek Bielicki

09/01/2023, 9:07 AM
makes sense - thanks 👍
👍 1
o

Oleg Nenashev

09/01/2023, 9:19 AM
Yes, it is explicitly mentioned in the list of the breaking changes
In theory, the relocation pom for the old artifacts should have pointed you to the new artifact ID but I'm not 100% sure
t

Tom

09/01/2023, 2:12 PM
Hmmm..yeah, I think we should have put artifact ID relocations in the 
jre8
tombstones too.
@Oleg Nenashev do you see any issue with me re-pushing the 3.0.0 relocation POMs with this change? I don’t normally like mutating an existing version, but it seems unavoidable in this case.
Or maybe better to do both 3.0.0 and 3.0.1 with this change?
o

Oleg Nenashev

09/01/2023, 2:40 PM
Hmmm..yeah, I think we should have put artifact ID relocations in the 
jre8
tombstones too.
It was in the project I shared but likely gone missing 🙂
I would do 3.0.1
Or maybe we even ship the tombstone 3.0.1 artifact in the olf group ID with the dependency on new artifacts? I guess it would address some compat issues
t

Tom

09/01/2023, 2:43 PM
Not 100% sure what you mean @Oleg Nenashev, can you elaborate?
o

Oleg Nenashev

09/01/2023, 3:24 PM
I mean releasing an empty JAR with a dependency instead of relocation POM
Not a great idea for standalone tho
t

Tom

09/01/2023, 4:22 PM
I’ve added artifactId relocations to both the jre8 JARs now
Let’s see if that helps…
Powered by