|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MOJO-1976) Artifact exclusion ... Erik Pragt (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Kohsuke Kawaguchi (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Erik Pragt (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Erik Pragt (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MOJO-1976) Artifact exclu... Erik Pragt (JIRA)

Anders, thanks, found it, and it works now.
One thing which is not entirely clear yet: I see that it's possible to exclude using the includes and excludes now, which is great, but is it also possible to exclude a scope, in this case, test? Adding all the offending dependencies seems like a bit of extra maintenance, which I'd like to prevent, and worse, it wouldn't prevent someone from using these dependencies in the production code if I exclude them by artefact name.