[
http://jira.codehaus.org/browse/MNG-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234142#action_234142
]
Stuart McCulloch commented on MNG-4793:
---------------------------------------
Fixed in
http://github.com/sonatype/sisu/commit/4efc10f500dba7a4acfe91d782eebf71ff1f5d79
The problem was in container code that sets the TCCL for components with
lifecycles (contextualizable, initializable, etc.). The TCCL should be set to
whatever realm the component belongs to, in order for string-based lookups to
work as expected from lifecycle methods.
Unfortunately this container code did not take into account the possibility of
proxy classes, where the real component class (and the associated realm) is
further up the class hierarchy. The fix is to search the hierarchy until we
find a class which was loaded by a realm - and if we don't find one then we
just leave the TCCL set to the last context realm.
[Note: the proxy class in this case was one generated by the container for
situations where the same component implementation is used multiple times for
different hints - we need a way to disambiguate between each use of the
implementation when performing custom injection in Guice, and creating thin
proxies was the easiest way to achieve this as the custom injection is
performed per-type]
> Unable to obtain archiver for extension 'zip'
> ---------------------------------------------
>
> Key: MNG-4793
> URL: http://jira.codehaus.org/browse/MNG-4793
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.0-beta-3
> Environment: maven-3-beta-2, maven-3-beta-3
> Reporter: Paul Gier
> Attachments: build.log
>
>
> There seems to be a regression in maven-3-beta-3 related to the assembly
> plugin. When building a multi-module project using Maven 3-beta-3 I get the
> error "Unable to obtain archiver for extension 'zip'". This error does not
> happen with Maven 3-beta-2.
> I wasn't able to reproduce this problem with a smaller project. The source
> can be checked out from the jboss repo
> {code}
> svn co -r 107936 http://anonsvn.jboss.org/repos/jbossas/trunk
> {code}
> The problem can be seen running building certain modules.
> {code}
> mvn clean install -pl deployment,server,osgi/zip
> {code}
> I will try to narrow down the problem further if I have some time.
--
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
