You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/11/18 13:35:03 UTC
[jira] Closed: (MNG-4900) "Unresolveable build extension" when
using shade plugin and repositories in profile
[ http://jira.codehaus.org/browse/MNG-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4900.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.1
Assignee: Benjamin Bentmann
Fixed in [r1036433|http://svn.apache.org/viewvc?view=revision&revision=1036433].
The Shade Plugin invokes {{MavenProjectBuilder.build(File, ArtifactRepository, ProfileManager)}}, passing in {{null}} for the profile manager argument. This makes it effectively build a project instance without active profiles, thereby loosing repos, dependencies etc. from those profiles. And the local repo impl used by Maven 3.0 doesn't serve files which aren't available from the declared remote repos. I was close to moving this issue to the Shade Plugin itself but had to realize that there is apparently no way to fix it using the Maven 2.x APIs, oh well.
> "Unresolveable build extension" when using shade plugin and repositories in profile
> -----------------------------------------------------------------------------------
>
> Key: MNG-4900
> URL: http://jira.codehaus.org/browse/MNG-4900
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies, Settings
> Affects Versions: 3.0
> Environment: This problem does not occur in Maven 3.0-beta-2 and earlier. It only occurs in Maven 3.0-beta-3 and Maven 3.0
> Reporter: Paul Gier
> Assignee: Benjamin Bentmann
> Fix For: 3.0.1
>
> Attachments: build.log, pom.xml
>
>
> There seems to be a problem when the shade plugin tries to resolve plugin extensions using a repository specified in a profile (either in the pom or settings.xml). It only tries to resolve from central. I attached a sample pom to reproduce the problem, and the build output.
> The problem can be seen by running the package goal in Maven 3.0.
> {noformat}mvn clean package -Pjboss-public{noformat}
--
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