[MRESOLVER-161] Resolve circular dependency resolver -> maven -> resolver

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Component/s: Resolver
• Assignee: Unassigned
• Reporter: Tamas Cservenak
• Created: 23/Jan/21 18:43
• Updated: 10/Sep/23 12:30
• Resolved: 10/Sep/23 12:30

Description

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?

Rationale:

• "resolver demos" are just that: a showcase how to use resolver (with maven), but alas, maven-resolver is incomplete in this respect (as it lacks maven models, mode builder, etc), so the cycle is here due those bits. So, imo a separate project/repo is most probably justified for it, as they are NOT executed/run during maven-resolver build anyway, the fact they are broken (see MRESOLVER-162) was discovered by manually running them).