[jira] (MSHARED-280) reporting fails with Maven 3.1-A1/Eclipse Aether 0.9-M2

["Herve Boutemy (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MSHARED-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MSHARED-280:
----------------------------------

    Summary: reporting fails with Maven 3.1-A1/Eclipse Aether 0.9-M2  (was: reporting fails with Eclipse Aether 0.9-M2/Maven 3.1-A1)
    
> reporting fails with Maven 3.1-A1/Eclipse Aether 0.9-M2
> -------------------------------------------------------
>
>                 Key: MSHARED-280
>                 URL: https://jira.codehaus.org/browse/MSHARED-280
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-reporting-exec
>    Affects Versions: maven-reporting-exec-1.0.2
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: maven-reporting-exec-1.1
>
>
> cause of MSITE-683
> [DefaultMavenReportExecutor line 128|http://maven.apache.org/shared/maven-reporting-exec/xref/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.html#128] is using Sonatype Aether ExclusionsDependencyFilter  for MavenPluginManager.setupPluginRealm(...) API call at [line 267|http://maven.apache.org/shared/maven-reporting-exec/xref/org/apache/maven/reporting/exec/DefaultMavenReportExecutor.html#267] which is affected 
> by switching to Eclipse Aether
> We will need some tweaks in maven-reporting-exec to detect Eclipse Aether

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira