Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-2659

Maven Enforcer Plugin `bannedDependencies` rule failes to resolve dependencies correctly


    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Fedora 5.0.0
    • Component/s: f4-build-tools
    • Labels:
    • Environment:
      Linux xps13 4.4.0-101-generic #124-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux


      Fedora sub-modules cannot be build/verified/tested before their module dependencies are not installed in the local Maven repository. This exposes resolving dependencies and individual module testing to dependency errors (e.g. building against invalid Kernel API).

      A "clean machine" that has never seen Fedora before should be able to execute `mvn validate` and `mvn dependency:resolve` successful. When purging all Fedora related artifacts from the local Maven repository (or starting on a new machine) this is not possible anymore (see attached build report).

      Using `mvn install` every time changes have been made to separate modules not only takes too long, but also introduces the problem of "out-dated snaphots" in the local repository if dependencies have not been installed in the right order previously. It further corrupts IDE integration (as I noticed using IntelliJ) and seems to raise a problem for individual module testing.


      Running `mvn -am -pl fcrepo-kernel-modeshape validate` the build fails as soon as <bannedDependencies/> is added to the enforcer plugin configuration, even without any exclusions configured.



          Issue Links



              • Assignee:
                claussni Ralf Claussnitzer
                claussni Ralf Claussnitzer
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: