+1 (non-binding)

 * Downloaded apache-maven-4.0.0-beta-4-bin.zip
 * Checked SHA512
 * Used the staging repository for builds listed below
 * Used Maven 4-beta4 for building maven-plugin-tools
 * Used Maven 4-beta4 for building maven-plugin-testing
     o Build fails with "Found Banned Dependency:
       org.jline:jline:jar:3.26.3"
         + Used by maven-jline, itself used by maven-core
     o Compilation errors for classes/interfaces not found:
         + org.apache.maven.api.DependencyCoordinate
         + org.apache.maven.api.services.DependencyCoordinateFactory
         + org.apache.maven.api.services.DependencyCoordinateFactoryRequest
     o After ignore (-Denforcer.skip) or resolution, JUnit tests pass
 * Used Maven 4-beta4 for building maven-compiler-plugin
     o After ignore (-Denforcer.skip) or resolution of same build
       failures as above:
         + JUnit tests pass
         + 4 integration tests fail (65 pass), but I suspect that they
           are minor changes. Will investigate later.

A commit for fixing maven-plugin-testing (I only guessed the fixes) is there (it is not yet a pull request because it depends on the staging repository):

   
https://github.com/Geomatys/maven-plugin-testing/commit/259ba19b17582b27cc7a93912b3db6a714b2d0e6

While I'm +1 (non-binding), it would be nice to fix the banned dependency issue if this is easy to do.

Martin

Reply via email to