|
||||||||
|
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)

@bodiam excluding dependencies by (e.g. test) scope would be a separate RFE.
(I am not sure why this is not the default anyway; there is not much use case for requiring that test-scope artifacts be compliant with a given bytecode version, other than making sure that the build can be run on a given version of the JDK, which is more easily accomplished with the enforcer rule for Java version. In practice you are only likely to care about compile- and runtime-scoped artifacts.)