[ http://jira.codehaus.org/browse/MNG-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-3237: ----------------------------------- Component/s: (was: Plugin Requests) Plugins and Lifecycle Artifacts and Repositories > Maven seems to ignore mirror-settings when searching for Reporting-plugins > -------------------------------------------------------------------------- > > Key: MNG-3237 > URL: http://jira.codehaus.org/browse/MNG-3237 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories, Plugins and Lifecycle, Sites > & Reporting > Affects Versions: 2.0.7 > Reporter: Helge Stieghahn > Assignee: Brett Porter > > In our company we have set up an Maven-Proxy that uses our > department-repository as source also. We have defined the Proxy aus Mirror > for maven-central in settings.xml so we don't have to bother with defining > repositories within all projects. that works fine for plugins from our > department-repository that are defined within the build-section, but does not > for ones that are defined within the reporting section of the pom. The error > message states that there is no such plugin or no valid version is found. If > we now define a pluginRepository-entry for the department-repository the > plugin will be found. It seems that the dependency-resolution for > reporting-plugins is ignoring the mirror-definition within the settings.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira