Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Sat, 2 Jun 2012 20:06:23 +0000 (UTC)
From: "Stefan Bodewig (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <1738043817.30880.1338667583249.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1097119140.7410.1334066359488.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (LOG4NET-333) AssemblyVersionAttribute should
 specify less precise version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefan Bodewig resolved LOG4NET-333.
------------------------------------

    Resolution: Won't Fix

Simon is right, we did have releases that have broken binary compatibility (1.2.11 has been one).

I'd recommend using binding redirects as well.
                
> AssemblyVersionAttribute should specify less precise version
> ------------------------------------------------------------
>
>                 Key: LOG4NET-333
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-333
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>            Reporter: Andrew Arnott
>            Priority: Minor
>             Fix For: 1.2 Maintenance Release
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The [AssemblyVersionAttribute("1.2.10")] that appears in the log4net.dll causes the CLR to refuse to load it if anyone was compiled against even a slightly different version. Yet most of these versions are (presumably) binary compatible.
> The work here is to adjust AssemblyVersionAttribute, while preserving AssemblyFileVersionAttribute:
> [AssemblyVersionAttribute("1.2")]
> [AssemblyFileVersionAttribute("1.2.10")]
> This way, folks can see what precise version it is, but at runtime anyone compiled against 1.2.x can run against other 1.2.x versions.
> This is particularly important in a heterogeneous system where multiple libraries are used that are all compiled against different versions of log4net and cannot all be recompiled against a common version of log4net.

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