[jira] Updated: (MNG-3540) No plugin update from a staged repository

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3540:
------------------------------

    Fix Version/s: 2.0.x

is this a regression? can you include the settings.xml you used?

> No plugin update from a staged repository
> -----------------------------------------
>
>                 Key: MNG-3540
>                 URL: http://jira.codehaus.org/browse/MNG-3540
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.9
>         Environment: Maven 2.0.9,  JDK6, both linux and windows 
>            Reporter: Raphaël Piéroni
>             Fix For: 2.0.x
>
>         Attachments: with-nexus.txt, with-profile.txt
>
>
> The archetype plugin depends on other projects.
> One of them is staged along with the plugin in a
> staged repository.
> When i define that repository in settings.xml in a profile
> which is always activated (both repository and pluginRepository)
> and remove all references from archetype in my local repository.
> I then call mvn archetype:create-from-project.
> Maven downloads the plugin but don't download the dependencies
> there it fails to instantiate the first used class from these dependencies.
> The first attachment (with-profile.txt) holds the trace
> When i define the repository in nexus (grouping first the repository then 
> central in one url) and defining that url as mirror of central in my setting,
> Also using a fresh repository. I call the same goal, and it works.
> The second attachment (with-nexus.txt) holds the trace.

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