logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4NET-324) Method not found: 'log4net.Config.XmlConfigurator.Configure'
Date Sun, 03 Jun 2012 07:36:23 GMT

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

Stefan Bodewig resolved LOG4NET-324.

    Resolution: Won't Fix

Yes, you are right, we've broken binary compatibility.  There is no chance to rectify this
without doing the same again 8-)

I have used libraries compiled against 1.2.10 with 1.2.11 so the problem doesn't happen all
the time, it must get triggered under specific circumstances.

As for the "strong name horror".  We feel the new strong name with a key available to everybody
who wants to create a patched log4net is superior to the old setup.  But if you need the old
"strong name", you can simply use the "oldkey" binaries.  I can't see how this is a horror,
but of course I'm biased.
> Method not found: 'log4net.Config.XmlConfigurator.Configure'
> ------------------------------------------------------------
>                 Key: LOG4NET-324
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-324
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.11
>         Environment: Mono
>            Reporter: Frédéric Mestayer
>            Priority: Blocker
>         Attachments: project_error.png
> In 1.2.10, signature was :
> void log4net.Config.XmlConfigurator.Configure()
> 1.2.11 changes it to :
> ICollection log4net.Config.XmlConfigurator.Configure()
> ANY library using 1.2.10 in a project using 1.2.11 will cause the type Loader to raise
an Exception because the signature does not match.
> You should NEVER break the signature contract inside a minor release, i can't understand
why you did this (and the strong name horror, too).

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


View raw message