this is a question for Aether :) I'm not an Aether expert, can't really answer
But please cross-post, because this is interesting for everybody. Regards, Hervé Le samedi 18 octobre 2014 11:23:28 Christofer Dutz a écrit : > While looking for the answer to your question, I noticed that the > ConflictResolver seems to be using the JavaScopeDeriver which is of type > ScopeDeriver to implement the scope derivation. It seems the > JavaScopeDerives is the only implementation of ScopeDeriver. It seems that > this is all part of Aether. So let me rephrase my question: > > Would it be possible to add additional ScopeResolvers to Aether? > > Chris > > -----Ursprüngliche Nachricht----- > Von: Hervé BOUTEMY [mailto:herve.bout...@free.fr] > Gesendet: Samstag, 18. Oktober 2014 12:41 > An: Maven Developers List > Betreff: Re: Plugin mechanism for the ConflictResolver? > > Hi, > > I'm not an expert from that, but I'm interested to learn: will need some > pointers and probably unit tests. > > I have one key thought: do you know if it is done at Maven level (like in > Maven 2.x) or at Aether-level? > > Regards, > > Hervé > > Le samedi 18 octobre 2014 08:52:34 Christofer Dutz a écrit : > > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional > commands, e-mail: dev-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org