[jira] (MENFORCER-151) Artifact resolution not always on repository-chain

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MENFORCER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MENFORCER-151.
------------------------------------

    Resolution: Duplicate
      Assignee: Robert Scholte
    
> Artifact resolution not always on repository-chain
> --------------------------------------------------
>
>                 Key: MENFORCER-151
>                 URL: https://jira.codehaus.org/browse/MENFORCER-151
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>            Reporter: Jens Zastrow
>            Assignee: Robert Scholte
>         Attachments: reactortest.zip
>
>
> Artifact resolution in maven is not always made by repository access.
> When you have a parent/child1,child2 structure where child2 depends on child1 maven can build the structure without the need of the child1 artifact in the e.g. local repository, but using it directly from child1 (when build from parent). The current enforcer plugins lacks such support, with the effect that the child1-artifact is tried to load from the repository-chain - which fails.
> A workaround for the attached example is to place the enforcerplugin into the parent pom.xml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira