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

Just that I'm understanding it correctly:
From an architectual point of view I can imagine this, but it is based on a very strict naming convention (core and utils should never depend on ui).
I'm not sure if it's worth it to add something like this.
I think you can get the same result by banning *-ui in your corporate pom and have a separate ui-parent which accepts *-ui
If this is an additional feature for the standard enforcer rules, this should be moved to MENFORCER.