Details
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
- relates to
-
CMS-11834 javax.activation jar appearing in CMS due to Tika upgrade
- Closed
-
HSTTWO-4570 exclude junit from jexl transient dependencies
- Closed