Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-11824

Enforce provided & banned artifacts are not included in the build

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 13.1.1, 11.2.13, 12.6.3, 13.2.0
    • None
    • None
    • Pulsar
    • Platform 205 - Content Beans 2

    Description

      To be decided how to use this in our build process, one option is to add a project profile that can scan for unwanted artifacts. Example plugin configuration:

            <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-enforcer-plugin</artifactId>
              <version>3.0.0-M2</version>
              <executions>
                <execution>
                  <id>enforce-banned-dependencies</id>
                  <goals>
                    <goal>enforce</goal>
                  </goals>
                  <configuration>
                    <rules>
                      <bannedDependencies>
                        <excludes>
                          <exclude>junit</exclude>
                          <exclude>com.sun.activation:javax.activation</exclude>
                        </excludes>
                      </bannedDependencies>
                    </rules>
                    <fail>true</fail>
                  </configuration>
                </execution>
              </executions>
            </plugin>
       

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              abanck Arent-Jan Banck (Inactive)
              CI/CD Chapter CI/CD Chapter
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: