Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[MRESOLVER-471] Resolver should be oblivious about scopes. #412

Merged
merged 3 commits into from
Jan 24, 2024
Merged

[MRESOLVER-471] Resolver should be oblivious about scopes. #412

merged 3 commits into from
Jan 24, 2024

Commits on Jan 24, 2024

  1. [MRESOLVER-471] Resolver should be oblivious about scopes. 

    In Resolver 1.x it defined scopes (that were redefined by consumer
project Maven), leading to duplication and possible digression if
Maven was about to support new dependency scopes. Moreover, Resolver
1.x also contained (based on these scopes) logic, "scope refinement",
"scope derive to buildpath scope" and so on. All these logic just
like the definition of scopes belong to consumer project: Maven.

Resolver really cares about only one scope: "system", as dependencies
in this scope should be handled very differently than others (have
no POMs and just file presence should be checked on resolving them).

---

https://issues.apache.org/jira/browse/MRESOLVER-471
    @cstamas
    cstamas committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    58aa550 View commit details
    Browse the repository at this point in the history

  2. Reformat

    @cstamas
    cstamas committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    06a1e04 View commit details
    Browse the repository at this point in the history

  3. Depreate session supplier as well 

    This class will need to be moved to Maven maven-resolver-provider.
    @cstamas
    cstamas committed Jan 24, 2024
    Configuration menu
    Copy the full SHA
    ee555a0 View commit details
    Browse the repository at this point in the history