[
http://jira.codehaus.org/browse/MNG-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3211.
-----------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2.x (to be reviewed))
Assignee: Brett Porter
Using the follow settings.xml and your scenario, it worked for me in 2.2.1 and
3.0-alpha-7
{code:xml}
<settings>
<localRepository>/Users/brett/test-runs/MNG-3211/local-repo</localRepository>
<profiles>
<profile>
<id>profile</id>
<pluginRepositories>
<pluginRepository>
<id>plugin</id>
<url>http://localhost:7777/archiva/repository/test</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>profile</activeProfile>
</activeProfiles>
</settings>
{code:xml}
> On call with full name Plugin groupId:artifatcId:version:goal , the
> ArtifactResolver is unable to resolve Plugins
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3211
> URL: http://jira.codehaus.org/browse/MNG-3211
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: Vincent Thoulé
> Assignee: Brett Porter
> Priority: Critical
>
> It appears that if Plugin is called using its full name Plugin
> groupId:artifactId:version:goal , the ArtifactResolver try to resolve
> Dependency Plugins only on central (http://repo1.maven.org/maven2).
> Detailed explanation :
> - I developped a Plugin identified as follow :
> > groupId : my.company
> > artifactId : maven-my-plugin
> > version : 1.0
> > available goal : goal
> 1) 1st Case :
> - With a pom.xml as follow
> <project >
> <modelVersion>4.0.0</modelVersion>
>
> <groupId>my.company</groupId>
> <artifactId>my-project</artifactId>
> <packaging>pom</packaging>
> <name>My Project</name>
> <version>1.0</version>
>
> <build>
>
> <plugins>
> <plugin>
> <groupId>my.company</groupId>
> <artifactId>maven-my-plugin</artifactId>
>
> <configuration>
> ...
> </configuration>
>
> </plugin>
> </plugins>
> </build>
> </project>
>
> - Executing "mvn my:goal" with new Maven Installation with empty local
> repository, from the directory where is stored locally this pom.xml ...
> My plugin is correctly downloaded from my Remote Maven Repository, and the
> goal successfully executed.
>
> 2) 2nd Case
> - Executing "mvn my.company:maven-my-plugin:1.0:goal" with new Maven
> Installation with empty local repository, from any directory ...
> My plugin is correctly downloaded from my Remote Maven Repository, and but
> its dependencies are not downloaded.
> It appears that Resolver try only to download dependencies from central
> (http://repo1.maven.org/maven2).
> pluginRepositories declared in settings.xml are ignored.
>
> Rgds
> V.
--
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
