Hey all,
Hit a weird issue this evening, today one of my builds started failing
with:
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy
(default-deploy) on project *****: A type incompatibility occurred while
executing org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy:
class org.apache.http.impl.client.BasicAuthCache cannot be cast to class
org.apache.http.client.AuthCache
(org.apache.http.impl.client.BasicAuthCache is in unnamed module of
loader org.codehaus.plexus.classworlds.realm.ClassRealm @23bd047f;
org.apache.http.client.AuthCache is in unnamed module of loader
org.codehaus.plexus.classworlds.realm.ClassRealm @3f5f79d8)
This is using Maven 3.9.14.
I traced this down to an in-house Mojo upgrade I released, which, in
part, upgraded `org.apache.maven.resolver:maven-resolver-*` from 1.9.25
to 1.9.27.
This had also caused a similar AuthCache error with the
`build-helper-maven-plugin` - being a patch release, I wouldn’t have
expected any breaking issues.
I declare my dependencies as `provided`, but I guess once they’re
compiled with the newer versions, the bytecode is already poisoned.
Is this a known regression?
