maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5591) Installing workspace reader triggers MNG-5503
Date Mon, 03 Mar 2014 09:56:59 GMT

    [ https://jira.codehaus.org/browse/MNG-5591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342302#comment-342302
] 

Stuart McCulloch commented on MNG-5591:
---------------------------------------

Just to confirm that this behaviour is expected. When you lookup a role the Plexus semantics
are that the "default" hint has highest priority, followed by any other hints - no guarantee
is given to the order of these secondary hints. (although the ordering typically reflects
the realm order where the implementation was bound, and the order of the class on the realm
classpath).

Note that in the latest Sisu release you can use @Priority(int) to explicitly enforce ordering
between components.

> Installing workspace reader triggers MNG-5503
> ---------------------------------------------
>
>                 Key: MNG-5591
>                 URL: https://jira.codehaus.org/browse/MNG-5591
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.2.1
>            Reporter: Mikolaj Izdebski
>            Assignee: Igor Fedorenko
>             Fix For: 3.2.2
>
>         Attachments: 0001-MNG-5591-Set-role-hint-for-ReactorReader-to-default.patch,
dummy-extension.tar.gz
>
>
> It looks like Maven 3.2.1 introduced a regression.  Installing
> extension which provides workspace reader triggers MNG-5503.
> Maven resolves artifacts from reactor, workspace, repositories (in
> that order).  In standard Maven distribution there is no workspace,
> but Maven provides an extension point which allows extensions to
> install workspace reader by providing a component with role
> {{org.eclipse.aether.repository.WorkspaceReader}} and role hint {{ide}}.
> Installing workspace reader extension in Maven 3.2.1 triggers a
> regression - Maven fails to resolve artifacts produced by reactor
> build (MNG-5503).  Even though artifact is present in reactor Maven
> queries workspace about it and if artifact is not found there it
> continues with repositories.  Expected behaviour is resolving artifact
> from reactor.
> Steps to reproduce this:
> 1) download and extract {{apache-maven-3.2.1-bin.tar.gz}}
> 2) download dummy-extension.tar.gz and build it with {{mvn package}}
> 3) download reproducer for MNG-5503 from: https://bugzilla.redhat.com/attachment.cgi?id=784786
> 4) try to build reproducer project, it succeeds
> 5) copy {{dummy-extension-1.0.0.jar}} to Maven {{lib/ext}}
> 6) try to build reproducer project, it fails
> When repeating the same steps for Maven 3.1.1 failure is not reproducible.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message