logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Psenner <dpsen...@gmail.com>
Subject Re: [VOTE] Release Apache log4net 1.2.14 based on RC1
Date Mon, 19 Oct 2015 12:56:08 GMT
Hey Gary,

is E: a network share?

On 2015-10-19 14:40, Gary Gregory wrote:
> Hm, something is missing with my set up running "build.cmd compile-all":
>
> LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
> NANTEXE_PATH is nant.exe
> BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
> log4net:ERROR XmlConfiguratorAttribute: Exception getting 
> ConfigurationFileLocation. Must be able to resolve 
> ConfigurationFileLocation when ConfigFile and ConfigFileExtension 
> properties are not set.
> System.Security.SecurityException: Request for the permission of type 
> 'System.Security.Permissions.FileIOPermission, mscorlib, 
> Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
>    at System.Security.CodeAccessSecurityEngine.Check(Object demand, 
> StackCrawlMark& stackMark, Boolean isPermSet)
>    at System.Security.CodeAccessPermission.Demand()
>    at System.AppDomainSetup.VerifyDir(String dir, Boolean normalize)
>    at 
> log4net.Config.XmlConfiguratorAttribute.ConfigureFromFile(Assembly 
> sourceAssembly, ILoggerRepository targetRepository)
> The action that failed was:
> Demand
> The type of the first permission that failed was:
> System.Security.Permissions.FileIOPermission
> The Zone of the assembly that failed was:
> Internet
>
> Unhandled Exception: System.Security.SecurityException: Request for 
> ConfigurationPermission failed while attempting to access 
> configuration section 'nant'. To allow all callers to access the data 
> for this section, set section attribute 'requirePermis
> sion' equal 'false' in the configuration file where this section is 
> declared. ---> System.Security.SecurityException: Request for the 
> permission of type 'System.Configuration.ConfigurationPermission, 
> System.Configuration, Version=4.0.0.0, Culture=neu
> tral, PublicKeyToken=b03f5f7f11d50a3a' failed.
>    at System.Security.CodeAccessSecurityEngine.Check(Object demand, 
> StackCrawlMark& stackMark, Boolean isPermSet)
>    at System.Security.CodeAccessPermission.Demand()
>    at 
> System.Configuration.BaseConfigurationRecord.CheckPermissionAllowed(String 
> configKey, Boolean requirePermission, Boolean isTrustedWithoutAptca)
>    --- End of inner exception stack trace ---
>    at 
> System.Configuration.BaseConfigurationRecord.CheckPermissionAllowed(String 
> configKey, Boolean requirePermission, Boolean isTrustedWithoutAptca)
>    at 
> System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, 
> Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, 
> Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
>    at System.Configuration.BaseConfigurationRecord.GetSection(String 
> configKey)
>    at System.Configuration.ConfigurationManager.GetSection(String 
> sectionName)
>    at NAnt.Console.ConsoleStub.Framework.GetRuntimeFramework()
>    at NAnt.Console.ConsoleStub.Main(String[] args)
>
> ?
>
> Gary
>
> On Sun, Oct 18, 2015 at 3:39 AM, Stefan Bodewig <bodewig@apache.org 
> <mailto:bodewig@apache.org>> wrote:
>
>     On 2015-10-18, Gary Gregory wrote:
>
>     > I've never built this guy before. Do you have a BUILDING.txt or
>     > instructions on a Wiki on how to validate an log4net RC?
>
>     http://logging.apache.org/log4net/release/building.html
>
>     Forget all the Visual Studio stuff and go to "NAnt".  You should use
>     NAnt 0.92, 0.91 will be fine for Windows as well.
>
>     If you'd like to validate all DLLs, then you are in for a hunt and
>     very
>     likely need an MSDN subscription to get hold of ancient versions
>     of .NET
>     - so don't even try to do that.  Buiding the relase involved combining
>     artifacts built on four different machines (for really old Mono, XP -
>     non networked - for really old .NET, recent Mono and recent .NETs).
>
>     If you've got access to a recent Windows system and a recent .NET SDK,
>     you'll likely only manage to build the .NET 4.0 and 4.5 assemblies.
>     Likewise on a recent Linux distro with recent Mono packages you'll
>     only
>     receive the mono-3.5 and mono-4.0 binaries.
>
>     Cheers
>
>             Stefan
>
>
>
>
> -- 
> E-Mail: garydgregory@gmail.com <mailto:garydgregory@gmail.com> | 
> ggregory@apache.org <mailto:ggregory@apache.org>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com 
> <http://garygregory.wordpress.com/>
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Mime
View raw message