maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (MNG-3540) No plugin update from a staged repository
Date Wed, 07 Apr 2010 08:05:35 GMT


Brett Porter closed MNG-3540.

       Resolution: Duplicate
    Fix Version/s:     (was: 2.2.x (to be reviewed))
         Assignee: Brett Porter

working in 3.0-alpha-7

> No plugin update from a staged repository
> -----------------------------------------
>                 Key: MNG-3540
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.0.9
>         Environment: Maven 2.0.9,  JDK6, both linux and windows 
>            Reporter: Raphaël Piéroni
>            Assignee: Brett Porter
>         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:
For more information on JIRA, see:


View raw message