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-491] Resolver should not have any "predefined" scope #425

Merged
merged 5 commits into from
Feb 7, 2024
Merged

[MRESOLVER-491] Resolver should not have any "predefined" scope #425

merged 5 commits into from
Feb 7, 2024

Commits on Feb 6, 2024

  1. [MRESOLVER-491] Resolver should not have any "predefined" scope 

    It is duty of consumer application to define those. Also,
no need for SPI either, as essentialy ONLY the dependency
managers were using the "system" scope definition so far.

Now, client code, that instantianates these anyway are
able to pass in predicate.

---

https://issues.apache.org/jira/browse/MRESOLVER-491
    @cstamas
    cstamas committed Feb 6, 2024
    Configuration menu
    Copy the full SHA
    178bec2 View commit details
    Browse the repository at this point in the history

  2. Tidy up

    @cstamas
    cstamas committed Feb 6, 2024
    Configuration menu
    Copy the full SHA
    7b29756 View commit details
    Browse the repository at this point in the history

  3. Reformat

    @cstamas
    cstamas committed Feb 6, 2024
    Configuration menu
    Copy the full SHA
    300b47f View commit details
    Browse the repository at this point in the history

  4. Simplify

    @cstamas
    cstamas committed Feb 6, 2024
    Configuration menu
    Copy the full SHA
    5ebdeca View commit details
    Browse the repository at this point in the history

Commits on Feb 7, 2024

  1. Use constants for the system predicate

    @gnodet
    gnodet committed Feb 7, 2024
    Configuration menu
    Copy the full SHA
    9c8610a View commit details
    Browse the repository at this point in the history