You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by bo...@apache.org on 2013/10/09 16:01:26 UTC
svn commit: r1530611 - /logging/log4net/trunk/src/site/xdoc/release/faq.xml
Author: bodewig
Date: Wed Oct 9 14:01:26 2013
New Revision: 1530611
URL: http://svn.apache.org/r1530611
Log:
LOG4NET-397 expand a little on the problems people may face with the two different strong name keys
Modified:
logging/log4net/trunk/src/site/xdoc/release/faq.xml
Modified: logging/log4net/trunk/src/site/xdoc/release/faq.xml
URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/site/xdoc/release/faq.xml?rev=1530611&r1=1530610&r2=1530611&view=diff
==============================================================================
--- logging/log4net/trunk/src/site/xdoc/release/faq.xml (original)
+++ logging/log4net/trunk/src/site/xdoc/release/faq.xml Wed Oct 9 14:01:26 2013
@@ -332,6 +332,26 @@ limitations under the License.
</p>
<p>
+ If you are creating an assembly that is likely to
+ be combined with other assemblies that depend on
+ the old strong name, then it is better you use the
+ oldkey assemblies as well.
+ </p>
+
+ <p>
+ We currently plan to distribute the new-key
+ assembly under a different name while providing
+ old and newkey <code>log4net.dll</code> assemblies
+ holding type forwards to the new assembly. This
+ may create a cleaner migration path for projects
+ that have dependencies using both versions.
+ At the moment such projects will either need to
+ use the GAC or create sub-directories inside the
+ application directory and configure assembly
+ probing with a <code>privatePath</code>.
+ </p>
+
+ <p>
Note that the "new" strong name no longer provides
any kind of authenticity. If you want to be sure
you have the "real" Apache log4net, download the binary