Uploaded image for project: 'Maven Resolver'
  1. Maven Resolver
  2. MRESOLVER-284

BREAKING: Some Sisu parameters needs to be bound

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.9.0
    • Resolver
    • None

    Description

      This is more a "documentation" or heads-up issue.

      Integrators of Resolver using Eclipse Sisu should bind at least following "configuration properties" to @Parameters

      • aether.syncContext.named.factory
      • aether.syncContext.named.nameMapper

      For example how to do it refer here: 

      If using plain Eclipse Sisu, see https://www.eclipse.org/sisu/docs/api/org.eclipse.sisu.inject/reference/org/eclipse/sisu/Parameters.html

      If using Plexus Shim see here:
      https://github.com/apache/maven/pull/831

      In short, some components now expect "parameters" to be injected from ctor (so container sourced) instead of session.

      Integrators not using Eclipse Sisu are left with hopefully sensible defaults.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            cstamas Tamas Cservenak
            cstamas Tamas Cservenak
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment