Hi, Im currently struggling with some changes introduced with Maven 3.1 explicitly regarding the ConflictResolver in conjunction with custom scopes. I know that these are generally not supported, but they had been working nicely for years. With Maven 3.1 it seems the scope of transitive dependencies of custom scope artifacts are all flattened to runtime.
Now to me it seems as if it were possible to support custom scopes by making the ConflictResolver modularizable. Currently all rules are hard-coded. How about defining an interface in which, in case of a custom scope maven will sonsult a ConflictResolver registered for that type of scope. This way plugins not designed for building Java applications could define how to deal with transitive dependencies of custom scopes? What do you think? Am I missing something here? Would I start hurting Kittens again ;-) ? Chris
