This issue has been fixed in SVN for the past couple weeks. The only external dependency IBatisNet has now is on Castle Dynamic Proxy.
Its possible to use IBatisNet with log4net 1.2.0 beta 8, log4net 1.2.9 beta, NLog, MS Logging Block, etc. --- Bob Hanson <[EMAIL PROTECTED]> wrote: > Thanks for the reply. I know it has been discussed before so I was > surprised > that a search couldn't find anything. > > I decided to just re-build SVN179390 with log4net 1.2.9 > > This is an annoying issue when you consider a project like Spring > that is > designed to remove dependencies. Yet you end up with build dependency > issues. We had "DLL hell". I wonder what cutsie name this gets. > > I'm not sure why assemblies should need to dump all of the assemblies > they > reference into a common bin directory. It would seem to me that some > kind of > solution could be created so that a referenced assembly goes to the > bin > directory but its own local references are copied to a sub-directory > or some > other location. > > So you'd end up with something like: > MyApp/bin/MyApp.exe > MyApp/bin/AnAssemblyReference.dll > MyApp/bin/AnAssemblyReference/*.dll (assemblies that > AnAssemblyReference.dllreference) > > You could also allow an assembly to be marked as "locally global" (or > some > such name) which simply shares it in the main bin directory. > > There probably are some good reasons why it's not that simple but > it's > easier for me to just speculate rather than investigate. :) > > On 9/27/05, Chad Humphries <[EMAIL PROTECTED]> wrote: > > > > Bob, > > > > This was on the list a bit back. I wasn't able to find a link to > the > > original post so here is the summary. > > > > This link > > http://forum.springframework.net/viewtopic.php?p=827&highlight=#827 > > lists the web.config entry for a binding redirect. I believe you > have > > to add a reference to the new log4net to your web project as well. > > The new version of ibatis will have a logfactoryadapter to remove > > these kind of issues. > > > > -Chad > > > > On 9/27/05, Bob Hanson <[EMAIL PROTECTED]> wrote: > > > I tried searching for this topic but found no matches. > > > > > > I recently put my current project into pseudo-production. i.e. > It's IN > > it's just not being used yet. :) > > > > > > Then Spring.NET came out with the 1.0 release right after I > released. I > > want to re-release with the latest version of Spring.NET since it's > the > > official release. However it is using log4net 1.2.9 and I think I'm > > experiencing a build problem between iBatis (SVN 179390) and > Spring. > > > > > > Should/can I re-build SVN179390 with log4net 1.2.9 or should/can > I do it > > with a different SVN version? > > > > > > Thanks, > > > Bob > > > > > >
