You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2013/09/16 02:39:52 UTC
[jira] [Commented] (NPANDAY-604) When a solution contains more than
one version of an assembly, only one version is used in POMs
[ https://issues.apache.org/jira/browse/NPANDAY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768013#comment-13768013 ]
Brett Porter commented on NPANDAY-604:
--------------------------------------
Fixed in r1523534
> When a solution contains more than one version of an assembly, only one version is used in POMs
> -----------------------------------------------------------------------------------------------
>
> Key: NPANDAY-604
> URL: https://issues.apache.org/jira/browse/NPANDAY-604
> Project: NPanday
> Issue Type: Bug
> Components: Project Importer
> Affects Versions: 1.4-incubating
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> When the project importer reviews references, it uses {{AppDomain.CurrentDomain.ReflectionOnlyAssemblies()}} to look at existing loaded assemblies and tries to match the assembly by short name. If not found it loads the DLL for reflection. This means once one version of an assembly is loaded, not different versions will later be loaded.
> Reflection loading in this case is unnecessary as {{AssemblyName.GetAssemblyName()}} contains all the information needed to construct the reference information without loading the assembly.
--
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