[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4net-dev
Subject:    [jira] [Updated] (LOG4NET-352) CS0419 during build with Mono >2.6
From:       "Dominik Psenner (JIRA)" <jira () apache ! org>
Date:       2012-09-03 6:59:07
Message-ID: 1406251219.29628.1346655547717.JavaMail.jiratomcat () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/LOG4NET-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Dominik Psenner updated LOG4NET-352:
------------------------------------

    Fix Version/s: 1.2.12
           Labels: mono  (was: )
    
> CS0419 during build with Mono >2.6
> ----------------------------------
> 
> Key: LOG4NET-352
> URL: https://issues.apache.org/jira/browse/LOG4NET-352
> Project: Log4net
> Issue Type: Bug
> Components: Builds
> Affects Versions: 1.2.11
> Environment: NAnt is 0.86 and Mono is 2.8.2
> NAnt is 0.91 and Mono is 2.10.8
> Reporter: Nikolay Orlyuk
> Assignee: Dominik Psenner
> Priority: Minor
> Labels: mono
> Fix For: 1.2.12
> 
> Attachments: log4net-r1380006-cref.patch.xz
> 
> 
> Fails to build with Mono > 2.6 with warn CS0419 treated as error.
> While cref contains argument type signature compiler complains with error: \
> Ambiguous reference in cref attribute `log4net.Appender.AppenderSkeleton.DoAppend'. \
> Assuming {quote}`log4net.Appender.AppenderSkeleton.DoAppend(log4net.Core.LoggingEvent)' \
> but other overloads including \
> `log4net.Appender.AppenderSkeleton.DoAppend(log4net.Core.LoggingEvent[])' have also \
> matched{quote} See [mail \
> archive|http://mail-archives.apache.org/mod_mbox/logging-log4net-user/201110.mbox/%3C8762k4m6oq.fsf@v35516.1blu.de%3E] \
> and [pastebin|http://pastebin.com/hpPaipXX] Note that using signature \
> "M:AppenderSkeleton.DoAppend(LoggingEvent)" as per [B.3.1 ID string \
> format|http://msdn.microsoft.com/en-us/library/aa664807%28VS.71%29.aspx] helps to \
> resolve this issue.

--
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


[prev in list] [next in list] [prev in thread] [next in thread]