As you've probably come to realize, the Logging Services Project isn't always the fastest moving group :-) Here's my thoughts on the matter...
Is it possible to create some sort of commons-logging plugin that uses J#/log4net internally? I got bad vibes from seeing the log4j constants redifined in Priority.jsl, Level.jsl. etc. Will you have to manually update that code for log4j 1.3 and/or 1.3.x? I've been doing .Net development ever since the release of 1.0 and I think you're the second J# developer I've come across (the first being the author of iTextSharp). I think most of the lack of feedback on your module is that there aren't a lot of J# developers out there. You're the first developer I've met who needs to build their project from the same source code. I wouldn't get too disappointed if you aren't seeing a large demand for your code. You're in a niche that many people aren't in. Correct me if I'm wrong but isn't J# only compatibile up to JDK 1.1? According to the copyright notice on this page: http://sunsite.tus.ac.jp/java/JDK1.1/docs/ 1.1 was released around 1997. Would that be akin to wanting to support Netscape 4.x in an AJAX enabled web application? While its entirely possible...its probably easier to require to user to upgrade to a more modern browser. Let's get back on track... One of the ideas I had for solving your problem was to recommend you make your own ILog and LogManager and load either log4net or log4j at runtime. I learned this was a feature that was introduced in JDK 1.2. You don't have to host a project on SourceForge to make it open source. There are plently of well written utils that are hosted on blogs that have been around for a while. The two that I think of right away are Cropper: http://blogs.geekdojo.net/brian/articles/Cropper.aspx and the Blowery Http Compression Module for ASP.Net: http://www.blowery.org/code/HttpCompressionModule.html Perhaps you could start hosting your code on a blog and build a small community around that before going through the work of setting up a SourceForge project. Do you think your problem could be averted by having a special Ant script that compiles in log4j or a NAnt script that compiles in log4net support? I don't think having two build scripts for two development platforms is unresonable. My two cents, Ron --- David Thielen <[EMAIL PROTECTED]> wrote: > Hi; > > > > I am working on some java code that we are porting to J#. Our goal is > to > have a common code base so we want to be able to call the log4j > classes that > we have throughout our code. > > > > However, we do not want to port log4j as log4net exists, and is > widely used > in the .net world. So I am creating a wrapper that is the public > log4j > classes that underneath calls log4net. I think this would be very > useful to > anyone trying to have a single codebase for J# and java. > > > > I asked the log4net group if they wanted it - but no answer. So is > there > someone out there who would be willing to set up a SourceForge > project for > this? > > > > Thanks - dave > > > > > > David Thielen > > 303-499-2544 > > <http://www.windwardreports.com> www.windwardreports.com > > > >
