eliasbalasis commented on issue #836:
URL: https://github.com/apache/maven-mvnd/issues/836#issuecomment-1751989419

   > @cstamas @eliasbalasis Re: Maven 3.8.x with Resolver 1.9.x: Yes, I do 
produce and sign those deliverables. Cherry-picked commits allowing people 
access new Resolver if thy can't/want/whatever upgrade. I will upgade those to 
1.9.15 shortly.
   
   @michael-o
   Did you have any opportunity to publish the latest version of "Resolver" ?
   
   
   
   > @guw this is definitely maven-resolver issue, but cannot say more without 
knowing more. Please try to enable "lock diag" (set _Java system property_ 
--not Maven property!) `aether.named.diagnostic.enabled=true`.
   > 
   > Edit: locking was introduced in Resolver 1.8.x but reworked/generalized in 
1.9.x lineage.
   
   It is with Java system property that I experimented but I never got any 
detailed output.
   
   Also as @cstamas mentioned further up:
   > And one more note: with latest Maven 3.9.4 you have option to collect 
"diagnostic data" for locking as well, and in case of those timeouts, it will 
spit out the diag data, see here 
https://maven.apache.org/resolver/maven-resolver-named-locks/index.html#diagnostic-collection-in-case-of-failures
   > 
   > ...
   > ...
   > 
   > Big fat note: use it ONLY with Maven 3.9.4 (actually, with resolver 
1.9.14+), as before, it emitted WRONG data (see 
[MRESOLVER-380](https://issues.apache.org/jira/browse/MRESOLVER-380)). This 
means mvnd is out of scope, as latest m7 uses older resolver....
   
   It seems Maven 3.9.x is the only effective way.
   However, I do vaguely recall having tried Maven 3.9.x at some point 
discovering some incompatibilities that I didn't have the time to explore, 
which may be implying that we are at a dead end.
   I have planned for an upgrade to Maven 3.9.x before the ned of this year, at 
which point I am expecting to stumble upon any incompatibilities and I will let 
you know.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to