Re: New version of maven-resolver causes failures in autopkgtests and builds

Hi Pierre,

That's unfortunate that two clojure packages with a near zero popcon 
block the transition of a core package of the Debian Java ecosystem. How 
can we avoid that and put the burden on updating the rdeps instead?

Looking at the pomegranate-clojure failure, the error is:

  ClassNotFoundException: 
org.eclipse.aether.named.providers.NoopNamedLockFactory

This class is in /usr/share/java/maven-resolver-named-locks.jar, which 
is a new jar in maven-resolver. So it's probably missing from a 
classpath somewhere.

Emmanuel Bourg


On 12/01/2025 21:16, Pierre Gruet wrote:
> Hi Emmanuel, and everyone,
> 
> I noticed that the new upstream version of maven-resolver, uploaded to 
> sid 27 days ago, failds to migrate because of two failing autopkgtests 
> in rdeps [0]. Also it is the root of #1091067 in scala, which would 
> cause its autoremoval in a few weeks.
> 
> Do you have any guess about the error messages that have been raised in 
> the various logs since the new maven-resolver got uploaded?
> 
> Thanks a lot for your help,
>