[ http://jira.codehaus.org/browse/MNG-358?page=all ]
     
John Casey resolved MNG-358:
----------------------------

    Resolution: Won't Fix

use <pluginRepositories/> instead.

See http://maven.apache.org/maven2/project-descriptor.html for more info.

> My own repo is consulted for parent POM's but not for plugins
> -------------------------------------------------------------
>
>          Key: MNG-358
>          URL: http://jira.codehaus.org/browse/MNG-358
>      Project: m2
>         Type: Bug
>   Components: maven-core
>     Versions: 2.0-alpha-1
>     Reporter: Peter van de Hoef

>
>
> It seems that plugins are only downloaded from the Maven repository and not 
> from user defined repo's. 
> Other dependencies are correctly downloaded from the user repository.
> I have the following situation.
> A parent POM (parent) a child POM (child) and a plugin (plugin).
> The child inherits from the parent and uses the plugin like:
>    <artifactId>child</artifactId>
>    ...
>    <parent>
>        <artifactId>parent</artifactId>
>        ...
>    </parent>
>    <build>
>        <plugins>
>            <plugin>
>                <artifactId>plugin</artifactId>
>                ...
>            </plugin>
>        </plugins>
>    </build>
>    <repositories>
>        <repository>
>            <id>my_own_repo</id>
>            ...
>        </repository>
>    </repositories>
> Furthermore I have my own remote repository (my_own_repo) to which these 
> artifacts have sucessfully been deployed.
> This repository is declared in the child POM.
> Now, when I remove all three artifacts from the local repository and try to 
> (re)build the child, the parent is automatically downloaded from the remote 
> repository but the plugin not.
> It seems that plugins are only downloaded from the Maven repository and not 
> from user defined repo's. 
> Other dependencies are correctly downloaded from the user repository.
> If I remove the <plugins> section from the <build> section and instead, 
> declare a dependency on the plugin like:
>    <dependencies>
>        <dependency>
>            <artifactId>plugin</artifactId>
>            ...
>        </dependency>
>    </dependencies>
> then the plugin is downloaded correctly from my own repo.
> If the plugin is specified in both the <dependencies> and the <plugins> 
> section, Maven will only consult the Maven repository.
> It appears that the <plugins> section has a higher priority than the 
> <dependencies> section.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to