[
https://issues.apache.org/jira/browse/NPANDAY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-255:
---------------------------------
Fix Version/s: (was: Backlog)
2.0
This has become worse with .NET 4.0 types added to the mix. They all used to
determine the right path to find them so that the artifact file can be set
correctly.
I believe that capability should be removed and the file set to null - I don't
think the artifact mechanism or plugins should be referring to the files
directly. For example the aspx plugin currently will copy those into the
package instead of assuming them to be present on the system which is likely
what's expected.
However, even if we do retain it, we should instead determine the right path
based on the target runtime framework rather than making the user specify it
per dependency. There may be some argument for allowing the user to specify the
architecture (as that is allowed in a full assembly name), but it should not be
required.
> Deprecate/Remove unessesary GAC types
> -------------------------------------
>
> Key: NPANDAY-255
> URL: https://issues.apache.org/jira/browse/NPANDAY-255
> Project: NPanday
> Issue Type: Bug
> Reporter: Lars Corneliussen
> Priority: Minor
> Fix For: 2.0
>
>
> Currently there are four GAC types.
> GAC ( "gac", null, "dll"),
>
> GAC_GENERIC ("gac_generic", null, "dll"),
>
> GAC_MSIL ("gac_msil", null, "dll"),
>
> GAC_32 ( "gac32", null, "dll");
> Does anybody know the difference? Which of them will be necessary in future
> versions?
> This should happen in conjunction with: Supporting alternative packaging
> types [url:http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=12402]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
