|
||||||||
|
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-1921) Ban dependencies by p... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Lennart Jorelid (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)
- [mojo-dev] [jira] (MOJO-1921) Ban dependencies... Baptiste Mathus (JIRA)

What you want to achieve here, Baptiste, seems quite similar to the ProjectType enumeration and corresponding enforcer rule defined in the Codestyle project of https://bitbucket.org/lennartj/nazgul_tools/.
Of course, in this case, the rules for GAVs and which dependencies are permitted into which projects are defined as plain EnforcerRules.
When in an enforcer rule, you have access to the full pom - so I didn't necessarily feel that more mechanics were required to enforce parts of the pom structure.