Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-7363

Demote Wagon as "only" transport supported

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

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Currently Maven uses some Resolver configurations as "baked in" that are wagon-only. Also, there are ITs that are testing Wagon configurations using Plexus XML, and are written originally for Maven 2. In short, these ITs should be disabled, as they assume that Maven uses Wagon (note: this was well BEFORE maven-resolver existed) and Wagon only, and configuration happens via Plexus XML not via officially supported Resolver properties.

      Issues (and ITs):

      • MNG-3652 - uses non-standard way to set up UA (see Resolver config)
      • MNG-3485 - is really about Wagon only
      • MNG-3599 - is about Wagon WebDAV extension
      • MNG-3600 - is about Wagon settings only (fileMode, dirMode, group)
      • MNG-4360 - is about Jackrabbit Wagon provider
      • MNG-4877 - uses SSH Wagon doing deploy via SSH
      • MNG-5175 - is about Wagon pooling

      Essentiall ITs are all for Maven2, also Maven3 but IMHO Maven4 should drop all these non-standard wagon-only tests (not have them run on Maven4).

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            cstamas Tamás Cservenák

            Dates

              Created:
              Updated:

              Slack

                Issue deployment