[jira] [Created] (MRESOLVER-161) Resolve circular dependency resolver -> maven -> resolver

["Tamás Cservenák (Jira)" <ji...@apache.org>]

Tamás Cservenák created MRESOLVER-161:
-----------------------------------------

             Summary: Resolve circular dependency resolver -> maven -> resolver
                 Key: MRESOLVER-161
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-161
             Project: Maven Resolver
          Issue Type: Task
          Components: Resolver
            Reporter: Tamás Cservenák


Apache Maven Resolver has a module {{maven-resolver-demo-snippets}} that in turn depends on Maven {{maven-resolver-provider}} that naturally depends on Maven Resolver.

Since MRESOLVER-154 is implemented, the "demo snippets" does not work: maven-resolver has class moved (introduced binary incompatibility), while maven-resolver-provider expects it in it's old place. All in all, this "cycle" is actually bad, as same issue will hit us with removal of service locator as well MRESOLVER-157.

Proposals: move the "resolver demos" out of resolver project completely, as it needs maven to make resolver usable with maven metadata/pom, but, due this cycle it puts everything into concrete, and harder to change thing. Or, any other idea?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)