Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-280

reporting fails with Maven 3.1-A1/Eclipse Aether 0.9-M2

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

Details

    Description

      cause of MSITE-683

      DefaultMavenReportExecutor line 128 is using Sonatype Aether ExclusionsDependencyFilter for MavenPluginManager.setupPluginRealm(...) API call at line 267 which is affected
      by switching to Eclipse Aether

      We will need some tweaks in maven-reporting-exec to detect Eclipse Aether

      Attachments

        Issue Links

        Activity

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

          People

            hboutemy Herve Boutemy
            hboutemy Herve Boutemy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment