DidierLoiseau commented on PR #1788:
URL: https://github.com/apache/maven/pull/1788#issuecomment-2400973468

   I see you have now disabled `MavenITmng2196ParentResolutionTest` so I guess 
it is not relevant anymore. 
   
   Regarding `MavenITmng7836AlternativePomSyntaxTest`, it succeeds when running 
the integration tests… _with maven built with this patch_. I also had this 
issue at some point, and after running the integration tests like that, it was 
gone, even when running under 3.9.7. However I now realize that it’s because 
the dependencies were in `` `pwd`/repo `` after the run under the patched Maven 
4. If the integration tests still have to run under Maven 3, then I suppose it 
would be good to understand what changes, and maybe something needs to be added 
to the `bootstrap.txt`.
   
   The thing is, `pom.hocon` uses parent `maven-extensions:41`, which has 
`maven-parent:41` as parent. The latter runs 
`spotless-maven-plugin:2.40.0:check`, which appears to need 
`palantir-java-format:2.38.0` which _is_ in the repository despite not 
appearing in spotless’ dependency tree. Palantir, however, depends on 
`error_prone_annotations:2.19.1` and `checker-qual:3.35.0`, which _are not_ in 
the repository. This seems a bit weird, but maybe there is a good reason for 
that?
   
   Changing the test to run with `-X 
-Dorg.slf4j.simpleLogger.showLogName=true`, you can see the following:
   ```
   [DEBUG] org.eclipse.aether.internal.impl.DefaultArtifactResolver - Resolving 
artifact com.google.errorprone:error_prone_annotations:pom:2.19.1 from [central 
(file:target/null, default, releases+snapshots), apache.snapshots 
(https://repository.apache.org/snapshots, default, snapshots)]
   [DEBUG] org.eclipse.aether.internal.impl.DefaultArtifactResolver - Resolving 
artifact org.checkerframework:checker-qual:pom:3.35.0 from [central 
(file:target/null, default, releases+snapshots), apache.snapshots 
(https://repository.apache.org/snapshots, default, snapshots)]
   [DEBUG] org.eclipse.aether.internal.impl.DefaultArtifactResolver - Resolving 
artifact com.google.errorprone:error_prone_annotations:pom:2.19.1 from [central 
(file:target/null, default, releases+snapshots), apache.snapshots 
(https://repository.apache.org/snapshots, default, snapshots)]
   [DEBUG] org.eclipse.aether.internal.impl.DefaultArtifactResolver - Resolving 
artifact org.checkerframework:checker-qual:pom:3.35.0 from [central 
(file:target/null, default, releases+snapshots), apache.snapshots 
(https://repository.apache.org/snapshots, default, snapshots)]
   [WARNING] 
org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory - The 
POM for org.checkerframework:checker-qual:jar:3.35.0 is missing, no dependency 
information available
   [WARNING] 
org.apache.maven.internal.aether.DefaultRepositorySystemSessionFactory - The 
POM for com.google.errorprone:error_prone_annotations:jar:2.19.1 is missing, no 
dependency information available
   ```
   For some reason however, this does not cause the build to fail on 
4.0.0-beta-4 or the current master, but it does with the 
`TransitiveDependencyManager`.
   
   It’s getting late so I’ll stop my investigations for today, but I put the 
test ouptut (with full stacktrace at the end) [as a gist 
here](https://gist.github.com/DidierLoiseau/679103e1338b12168170fdcc5ea5e1d9).


-- 
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