[mojo-dev] [jira] (MOJO-1921) Ban dependencies by pattern on both deps and current artifact

[Baptiste Mathus (JIRA)]

Baptiste Mathus commented on MOJO-1921 Ban dependencies by pattern on both deps and current artifact Well, I'm actually sure we at least would use it . Granted, in an ideal world, one would have a parent pom by project typology, but I just thought this would be a bit too limiting for one wanting to use it. From a quick look in the code, currently the standard BannedDependencies code actually doesn't support anything like -ui. (Only strictly '' in '*:someartifactid' is for example processed specially to just kind of ignore the groupId). I agree this might be a good idea to just evolve the existing BannedDependencies in MENFORCER. I initially thought doing so, but then I preferred not risk impacting current behaviour of the rule. But after a good sleep, I think you have a point. This should be possible to modify that rule without having a very high risk of being non backward compatible. This would be better from a Maven User PoV to not have many rules that does almost but not quite the same thing. I guess this could be something I could do through the "committer school" context . Thanks a lot for your feedback. It's cool!

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

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email