Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-1589

Excluded artifacts from bomGenerator still end up in the maven repo

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • Ongoing Prod
    • None
    • team/prod
    • None
    • False
    • False

      After adding some more exclusions for Spring Boot artifacts[1] they end up disappearing from the generated BOM as expected, but our QE reported that they still end up in the maven repository[2].

      I guess this may be because the Kogito BOM is an input to the BOM generator and they are determined by PNC to be dependencies and thus end up in the maven repository.

      I am wondering if there is a solution here beyond just adding them to a list in the bacon config, something like:

        repositoryGeneration:
          excludeArtifacts:
            - 'org.kie.kogito:.*spring-boot.*:.*'
            - 'org.kie.kogito:.*springboot.*:.*'

      I haven't tested the above exclusion patterns (yet), but you get the idea (and yes we have both spring-boot and springboot artifacts ).

      [1] https://code.engineering.redhat.com/gerrit/plugins/gitiles/quarkusio/quarkus-platform/+/refs/changes/23/289123/14/pom.xml#436
      [2] https://download.eng.bos.redhat.com/rcm-guest/staging/quarkus/Members/Kogito/quarkus-2.2.3.DR1/

              ant@redhat.com Ant Stephenson
              ant@redhat.com Ant Stephenson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: