[
https://jira.codehaus.org/browse/MNG-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354820#comment-354820
]
Florian Zschocke commented on MNG-4900:
---------------------------------------
I have come across a similar problem with the versions-maven-plugin, which
seems not to be solved by this fix. In general I don't quite understand the
fix, because while the active profiles are set by this even if no
ProfileManager is passed in, the repositories defined in the profiles never
make it into the list of repositories for the project build. Shouldn't the
repositories defined in the active profiles be added to the repository list in
the build request?
> "Unresolveable build extension" when using shade plugin and repositories in
> profile
> -----------------------------------------------------------------------------------
>
> Key: MNG-4900
> URL: https://jira.codehaus.org/browse/MNG-4900
> Project: Maven
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
