Skip to content

Align configuration properties #1783

Description

@cstamas

New feature, improvement proposal

The Resolver 2 configuration keys had renames (for ex, connector and transport was split in Aether 1.1, but some config keys meant for transport still had connector in them).

Make sure:

  • every renamed key still has a fallback to Resolver 1 one, if possible
  • maybe even undo some renames, unless it was "right thing to do"

Resolver 1: https://maven.apache.org/resolver-archives/resolver-1.9.25/configuration.html (warning: this table is manually maintained and is incomplete!)
Resolver 2: https://maven.apache.org/resolver/configuration.html

Best would to start with Resolver 2 properties (as they are complete as they are generated), and look up Resolver 1 counterpart, if applicable (ie. is not for new feature not existing in Resolver 1).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions