[
https://issues.apache.org/jira/browse/NPANDAY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-410.
----------------------------------
Resolution: Fixed
removed the need for this by having the .NET plugins run using a normal
appdomain instead of requiring an appdomain manager.
Cleaned up several pieces of code that came with the removal of the UAC/PAB so
that it is more consistent
> Attempt to install NPanday.Model.Pom to Global Assembly Cache fails the
> NPanday build without administrative access
> -------------------------------------------------------------------------------------------------------------------
>
> Key: NPANDAY-410
> URL: https://issues.apache.org/jira/browse/NPANDAY-410
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.4-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Assignee: Brett Porter
> Labels: mono
> Fix For: 1.4.1-incubating
>
>
> While building the NPanday.Model.Pom project on Linux, the following error is
> shown and the NPanday build fails.
> Failure adding assembly
> /home/jfallows/Workspaces/npanday-trunk/dotnet/assemblies/NPanday.Model.Pom/target/NPanday.Model.Pom.dll
> to the cache: gac directories could not be created, possibly permission
> issues.
> This error makes sense because the GAC in /usr/lib/mono/gac is owned by root
> so a normal user would not have write access.
> Other versions of NPanday.Model.Pom appear to be present in
> ~/.m2/uac/gac_msil. For example:
> {code}
> $ ls -l ~/.m2/uac/gac_msil/NPanday.Model.Pom
> drwxr-xr-x 2 jfallows jfallows 4096 2011-04-12 16:41 1.2.1__npanday.model
> {code}
> Would it be reasonable to install the NPanday.Model.Pom.dll to the same
> location during the NPanday trunk build?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
