[mojo-dev] [jira] (MOJO-1988) Make excluding test dependencies configurable

[Jesse Glick (JIRA)]

Title: Message Title

Jesse Glick commented on an issue   Re: Make excluding test dependencies configurable One approach would be to expand AbstractResolveDependencies.IgnorableDependency to allow you to specify scopes as well, and then make EnforceBytecodeVersion have a configurable list of dependencies, just like BanDuplicateClasses. This would be the most general: you could ignore certain dependencies by groupId, ignore provided-scope dependencies, etc. A potentially simpler approach would be to do filtering in AbstractResolveDependencies.getDependenciesToCheck. For some reason this uses DependencyTreeBuilder which I understand does not work so well in Maven 3, rather than using the standard MavenProject.getArtifacts, but at any rate this (or EnforceBytecodeVersion.filterArtifacts) could check for test-scope dependencies. Add Comment   Mojo / MOJO-1988 Make excluding test dependencies configurable In our deployment server, we are limited to Java 5. However, for our testing purposes, we are not limited at all and we can easily use Java 6/7 compatible dependencies. Therefor, it would be great if the plugin would allow the exclusion of certain artifacts by scope (and maybe excluding test dependencies should be excluded by default even). This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email