[
https://issues.apache.org/jira/browse/LOG4NET-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386458#comment-14386458
]
Stefan Bodewig commented on LOG4NET-344:
For some reason we've all forgotten
[
https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386494#comment-14386494
]
Stefan Bodewig commented on LOG4NET-442:
should we close this as Won't fix
[
https://issues.apache.org/jira/browse/LOG4NET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386242#comment-14386242
]
Stefan Bodewig edited comment on LOG4NET-437 at 3/30/15 8:37 AM
On 2015-03-30, Alexander Houben wrote:
You probably mean LOG4NET-455.
Yes, thanks!
Stefan
signature.asc
Description: PGP signature
[
https://issues.apache.org/jira/browse/LOG4NET-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386439#comment-14386439
]
Stefan Bodewig commented on LOG4NET-412:
I've found the code you use in
http
[
https://issues.apache.org/jira/browse/LOG4NET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-443.
Resolution: Fixed
Fix Version/s: 1.3.0
implemented the try/finally workaround
[
https://issues.apache.org/jira/browse/LOG4NET-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386511#comment-14386511
]
Stefan Bodewig commented on LOG4NET-438:
You put the appender into lossy mode
[
https://issues.apache.org/jira/browse/LOG4NET-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-438.
Resolution: Not a Problem
SmtpAppender not working
[
https://issues.apache.org/jira/browse/LOG4NET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-441.
Resolution: Fixed
added the suggested FAQ with svn revision 1670051 will update the site
[
https://issues.apache.org/jira/browse/LOG4NET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387959#comment-14387959
]
Stefan Bodewig commented on LOG4NET-437:
Oops, my fault. I deleted the classes
[
https://issues.apache.org/jira/browse/LOG4NET-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-71.
---
Resolution: Fixed
the reshuffling has been completed many months ago, right now the last open
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/12#issuecomment-87385635
I had to tweak things a little to make it build on Mono and it looks as if
I had to do a little bit more for .NET 2.0, these will be follow up commits
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/11#issuecomment-87388090
part of your patch has been done by a commit earlier today, but I
overlooked a few other places that you fixed, thanks!
Also added Mono 3.5.
---
If your
[
https://issues.apache.org/jira/browse/LOG4NET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385815#comment-14385815
]
Stefan Bodewig edited comment on LOG4NET-453 at 3/29/15 3:24 PM
[
https://issues.apache.org/jira/browse/LOG4NET-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-458:
---
Attachment: localsyslog.patch
The attached patch tries to cover things up in a threadsafe
[
https://issues.apache.org/jira/browse/LOG4NET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385815#comment-14385815
]
Stefan Bodewig commented on LOG4NET-453:
doesn't ManagedColoredConsoleAppender
[
https://issues.apache.org/jira/browse/LOG4NET-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-447.
Resolution: Fixed
Fix Version/s: 1.3.0
added PopAllEvents with svn revision 1669935
[
https://issues.apache.org/jira/browse/LOG4NET-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-456.
Resolution: Fixed
Fix Version/s: 1.3.0
Thanks, patch applied with svn revision
[
https://issues.apache.org/jira/browse/LOG4NET-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-455.
Resolution: Fixed
Fix Version/s: 1.3.0
applied modified version of PR with svn
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/13#issuecomment-78293988
I took a freedom to modify the patch a little
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/13#issuecomment-78291627
tracked by LOG4NET-457
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
[
https://issues.apache.org/jira/browse/LOG4NET-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-457.
Resolution: Fixed
fixed with svn revision 1665915
SMTP Appender should trim leading
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/12#issuecomment-77686089
I'm fine with the first batch of changes you propose but don't think we
should thrown an exception on .NET 4.0. I've opened
[LOG4NET-455](https://issues.apache.org/jira
Stefan Bodewig created LOG4NET-455:
--
Summary: LogicalThreadContext does not flow correctly through
async/await
Key: LOG4NET-455
URL: https://issues.apache.org/jira/browse/LOG4NET-455
Project
On 2015-03-07, Gert Kello wrote:
I'm still stuck
Sorry about that. It's been quite some time since I left the build
process in a two-third finished stage and I really should fix that.
I think it would be best if you opened a JIRA issue for it and I'll try
to figure out how to best do it. As
Github user bodewig commented on the pull request:
https://github.com/apache/log4net/pull/12#issuecomment-7734
FWIU the code should be compilable for .NET 4.0 but the changes will only
fix the problem on 4.5 (and there is no fix for 4.0).
We'll likely need additional
On 2015-02-20, Geoffrey Corey wrote:
Hi Apache Logging log4net,
Please fix your download page(s) by setting the execute bit on your CGI
files and committing the changes to subversion.
Done, thanks for the report!
Stefan
[
https://issues.apache.org/jira/browse/LOG4NET-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216286#comment-14216286
]
Stefan Bodewig commented on LOG4NET-446:
Actually the official way would
Hi
as Dominik said, the best place to discuss technical issues around
chages to log4net is this mailing list itself.
On 2014-10-15, Kanchan Mehrotra wrote:
We would like to discuss with you plans for releasing support for your
package for ASP.NET vNext
What kind of changes would log4net need
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017765#comment-14017765
]
Stefan Bodewig commented on LOG4NET-429:
Hmm. in that case any patch that tried
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017010#comment-14017010
]
Stefan Bodewig commented on LOG4NET-429:
CompositeProperties.Flatten is going
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-429:
---
Attachment: LOG4NET-429-alternative.patch
This is an alternative patch which has arguably
On 2014-06-01, Alexey Polyakov wrote:
I have encountered a heavy drop in performance after migration from log4net
1.2.10 to 1.2.13. My research pointed out to the commit #1511303 and
specifically to the line 1340:
eventProperties[UserNameProperty] = UserName;
Seems this is
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015049#comment-14015049
]
Stefan Bodewig commented on LOG4NET-429:
I like the way you've moved lifted
On 2014-04-17, Howe, Peter L wrote:
I am a contract employee at this company and my contract is ending and
I need to unsubscribe from this list. I cannot find anything on the
Apache web site to do so.
There is a header in each message frim this list :-)
list-unsubscribe:
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946483#comment-13946483
]
Stefan Bodewig commented on LOG4NET-429:
This is LOG4NET-421 as well, right
[
https://issues.apache.org/jira/browse/LOG4NET-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946483#comment-13946483
]
Stefan Bodewig edited comment on LOG4NET-429 at 3/25/14 1:09 PM
Sorry for the delay, Justin
On 2014-03-04, Justin Dearing wrote:
If I were to make an appender without the dependency on Wintellect's C++
code, could that be added to the log4net built in Appenders?
Would it have any other external dependency? I don't think we'd want to
add any new
On 2014-03-06, Justin Dearing wrote:
On Thu, Mar 6, 2014 at 5:07 AM, Stefan Bodewig bode...@apache.org wrote:
If I were to make an appender without the dependency on Wintellect's C++
code, could that be added to the log4net built in Appenders?
Would it have any other external dependency? I
[
https://issues.apache.org/jira/browse/LOG4NET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906955#comment-13906955
]
Stefan Bodewig edited comment on LOG4NET-423 at 2/20/14 1:39 PM
[
https://issues.apache.org/jira/browse/LOG4NET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-423:
---
Labels: rolling (was: )
The logs don’t appear working correctly. New logs are created
[
https://issues.apache.org/jira/browse/LOG4NET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906955#comment-13906955
]
Stefan Bodewig commented on LOG4NET-423:
Vaishali, this is log4net's bug tracker
[
https://issues.apache.org/jira/browse/LOG4NET-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-423:
---
Component/s: Appenders
The logs don’t appear working correctly. New logs are created
[
https://issues.apache.org/jira/browse/LOG4NET-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-418.
Resolution: Cannot Reproduce
of all the options I have with changing the state
On 2014-02-04, Miljenko Cvjetko wrote:
Hi
1. to split log4net-13.dll so that the main assembly can be used for
the client profile and a separate assembly contains the stuff that
requires System.Web - this way we no longer need the -cp builds.
Dominik convinced me there was no future for the
[
https://issues.apache.org/jira/browse/LOG4NET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869607#comment-13869607
]
Stefan Bodewig commented on LOG4NET-415:
Sorry for not responding for so long
[
https://issues.apache.org/jira/browse/LOG4NET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869607#comment-13869607
]
Stefan Bodewig edited comment on LOG4NET-415 at 1/13/14 3:19 PM
[
https://issues.apache.org/jira/browse/LOG4NET-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13864056#comment-13864056
]
Stefan Bodewig commented on LOG4NET-415:
I'm not a syslog expert, far from
On 2013-12-02, Dominik Psenner wrote:
Looks like I found a typo:
quite possible, I tried to fix the main solutions by hand, so please go
ahead and fix it. Also I think migrating the example and extension
solutions to VS2012 would be better than leavin in broken solutions.
And maybe the
[
https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834637#comment-13834637
]
Stefan Bodewig commented on LOG4NET-411:
The 3.5 CP assembly is not compatible
[
https://issues.apache.org/jira/browse/LOG4NET-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831359#comment-13831359
]
Stefan Bodewig commented on LOG4NET-409:
Ben, please forgive if I sounded as if I
[
https://issues.apache.org/jira/browse/LOG4NET-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-351:
Assignee: (was: Dominik Psenner)
sorry, need to reopen to remove the fix version
[
https://issues.apache.org/jira/browse/LOG4NET-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-351.
Resolution: Invalid
Fix Version/s: (was: 1.3.0)
Blue tooth is not connecting
[
https://issues.apache.org/jira/browse/LOG4NET-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831054#comment-13831054
]
Stefan Bodewig commented on LOG4NET-406:
I'm really on the fence here
On 2013-11-22, Dominik Psenner wrote:
Finally. :-)
Yeah. Jenkins has now two Windows slaves and the new one was added to
the roster before Nant was installed.
Stefan
Stefan Bodewig created LOG4NET-408:
--
Summary: Correction on InterProcessLock
Key: LOG4NET-408
URL: https://issues.apache.org/jira/browse/LOG4NET-408
Project: Log4net
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4NET-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-187.
Resolution: Fixed
added with svn revision 1544675
Add a Trace level with isTraceEnabled
[
https://issues.apache.org/jira/browse/LOG4NET-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-408.
Resolution: Fixed
svn revision 1544744.
Correction on InterProcessLock
On 2013-11-21, Christian Grobmeier wrote:
On 21 Nov 2013, at 8:15, Stefan Bodewig wrote:
On 2013-11-21, Christian Grobmeier wrote:
One no blocker which I just saw: the KEYS file is included in the
dist. Shouldn't it be left out?
I think we've always done it that way in log4net and I know
[
https://issues.apache.org/jira/browse/LOG4NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-376:
---
Fix Version/s: (was: 1.2.13)
Race condition in AbsoluteTimeDateFormatter
[
https://issues.apache.org/jira/browse/LOG4NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-376:
---
Fix Version/s: 1.2.13
Race condition in AbsoluteTimeDateFormatter
.
For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:
http://logging.apache.org/log4net/
Stefan Bodewig on behalf of the log4net community
-BEGIN PGP SIGNATURE-
Version: GnuPG
On 2013-11-21, Christian Grobmeier wrote:
+1
checked formalities, but didn't interpret the content b/c lack of
windows :-)
thanks.
One no blocker which I just saw: the KEYS file is included in the
dist. Shouldn't it be left out?
I think we've always done it that way in log4net and I know
So I count three +1s by Dominik, Christian and myself with no other
votes.
As usual I'll publish the distro and give the mirrors some time to catch
up before sending out the announcement and updating the site.
Stefan
On 2013-11-16, Dominik Psenner wrote:
Strange. Would you please do a safety check whether other things were
reverted too?
the other changes made in that revision look legit to me.
Sorry for not cathcing it when the commit was made.
Stefan
[
https://issues.apache.org/jira/browse/LOG4NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-376:
---
Fix Version/s: 1.3.0
1.2.13
Race condition in AbsoluteTimeDateFormatter
Hi all,
three times is a charm. :-)
Changes over RC2 is a packaging change (the 3.5 assemblies now contain
the ILogExtensions) and two bug fixes.
log4net 1.2.13 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/logging/log4net
(revision 3550)
Details of changes since
[
https://issues.apache.org/jira/browse/LOG4NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824405#comment-13824405
]
Stefan Bodewig commented on LOG4NET-376:
I'm afraid svn revision 1486883
http
[
https://issues.apache.org/jira/browse/LOG4NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-376:
---
Fix Version/s: (was: 1.2.12)
Race condition in AbsoluteTimeDateFormatter
On 2013-11-14, Dominik Psenner wrote:
I'm not sure whether setting the encoding to UTF8 triggers some sort of
different handling inside of the framweork's SMTP code even if the test
was pure ASCII. If it doesn't, then I'm fine with UTF8.
and checking a few of my Gmail's mails it seems they
On 2013-11-13, Dominik Psenner wrote:
To me it looks like I've broken the prior behaviour while trying to fix
LOG4NET-354 and LOG4NET-405 remedies that. *ouch*
I see
Quoting:
http://msdn.microsoft.com/en-us/library/system.net.mail.mailmessage.bodyenco
ding(v=vs.110).aspx
The default
On 2013-11-13, Dominik Psenner wrote:
Thought of that too, but I decided to let it be in UTF8 cause its the most
compatible format nowadays whereas ASCII is somewhat antique. What do you
think?
IIUC ASCII would have been the implicit body encoding for log4net
1.2.12 so when looking for a
Great to see you here, Gert!
On 2013-11-10, gert.drie...@telenet.be wrote:
no build for .NET 4.5, but I assume this was already discussed before
and is planned for a subsequent release
We introduced the 4.0 builds in 2011 mainly because of the new security
model. Without that the 2.0 version
On 2013-11-10, gert.drie...@telenet.be wrote:
Professionally I’m back to working with a .NET technology stack, so
I’ll also try find time to contribute to .NET OSS projects again.
very much looking forward to it.
Stefan
On 2013-11-07, Dominik Psenner wrote:
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see
Stefan Bodewig created LOG4NET-404:
--
Summary: assemblies for .NET 3.5 are missing ILogExtensions
Key: LOG4NET-404
URL: https://issues.apache.org/jira/browse/LOG4NET-404
Project: Log4net
[
https://issues.apache.org/jira/browse/LOG4NET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-404.
Resolution: Fixed
assemblies for .NET 3.5 are missing ILogExtensions
If there is, I'd be happy to wait anouther week, otherwise I'd proceed
with the release process and rather try to get trunk back into a
releasable state for a quick 1.3.0 afterwards.
Not anytime soon, sorry.
Understood. I'll have to re-tag anyway as my fix for what became
LOG4NET-404 was
[
https://issues.apache.org/jira/browse/LOG4NET-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reassigned LOG4NET-132:
--
Assignee: Stefan Bodewig
Environment variables are mistakenly case sensitive
[
https://issues.apache.org/jira/browse/LOG4NET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-387:
---
Priority: Critical (was: Blocker)
Fix Version/s: (was: 1.2.10)
I'm sure
[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-383.
Resolution: Fixed
Fix Version/s: 1.2.12
Log4Net.Error throws
[
https://issues.apache.org/jira/browse/LOG4NET-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-363.
Resolution: Duplicate
Fix Version/s: 1.2.12
System.ObjectDisposedException thrown
[
https://issues.apache.org/jira/browse/LOG4NET-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-132.
Resolution: Fixed
Environment variables are mistakenly case sensitive on windows
On 2013-11-06, Nick Williams wrote:
LOG4NET-393 is causing us some problems at $work. It's fixed as of
1.3.0, which doesn't appear to be released yet. Is there an expected
date for it to be released, and if not what can I do to help make this
happen?
If you need anything fast, then it is
[
https://issues.apache.org/jira/browse/LOG4NET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-391:
---
Issue Type: Improvement (was: Bug)
XmlLayoutSchemaLog4j does permit logging without
On 2013-11-06, Dominik Psenner wrote:
Since LOG4NET-393 is a blocker for people who work a lot with lambda
expressions and right now we have absolutely no idea as of when 1.3 will be
ready we might better release 1.2.13 containing the fix for the issue.
Yeah, no problem with that, I'll try to
[
https://issues.apache.org/jira/browse/LOG4NET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-394:
---
Fix Version/s: (was: 1.3.0)
1.2.13
Lambda-based ILog-Extensions
[
https://issues.apache.org/jira/browse/LOG4NET-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-393:
Assignee: Stefan Bodewig (was: Dominik Psenner)
Using dynamic methods with log4net
[
https://issues.apache.org/jira/browse/LOG4NET-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-393.
Resolution: Fixed
Fix Version/s: (was: 1.3.0)
1.2.13
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see anything
you feel fits and we'll go from
On 2013-11-05, Dominik Psenner wrote:
Having a general FRAMEWORK_X_Y define wouldn't be bad. But maybe
every
FRAMEWORK_X_Y should read as FRAMEWORK_X_Y_OR_ABOVE since
every framework
is compatible to its ancestors.
fine with me, I'll make the adjustments.
Awesome.
not yet done, but will
On 2013-11-05, Dominik Psenner wrote:
Glad you've been able to reproduce it, but I can't recall that I had a
firewall at all that could block me. But who knows - sometimes firewalls
behave more like invisiwalls. :-)
This is Jenkins, our CI now runs the tests (on .NET 4.0 for now).
Strange
On 2013-11-04, Dominik Psenner wrote:
Having a general FRAMEWORK_X_Y define wouldn't be bad. But maybe every
FRAMEWORK_X_Y should read as FRAMEWORK_X_Y_OR_ABOVE since every framework
is compatible to its ancestors.
fine with me, I'll make the adjustments.
Still I would keep these defines:
On 2013-11-03, Dominik Psenner wrote:
On 11/02/2013 10:41 AM, Stefan Bodewig wrote:
On 2013-11-01, Dominik Psenner wrote:
2013/11/1 Stefan Bodewig bode...@apache.org
I'd like restructure our codebase a little as it feels a bit scattered
to me, in particular I'd like to move
src/* = src
Hi all,
I have removed all defines that correspond to frameworks trunk no longer
builds and also dropped the *_2_0 symbols as they are the default now -
on that way I've removed a few chunks of 1.x specific code.
For the Compact Framework 2.0 build I'll ask Dustin Jones, the reporter
of
[
https://issues.apache.org/jira/browse/LOG4NET-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reassigned LOG4NET-71:
-
Assignee: Stefan Bodewig
Reorganise source repository to support multiple src projects
On 2013-11-01, Dominik Psenner wrote:
2013/11/1 Stefan Bodewig bode...@apache.org
I'd like restructure our codebase a little as it feels a bit scattered
to me, in particular I'd like to move
src/* = src/main/* (except for site)
tests = src/tests
examples = src/examples
extensions = src
Hi,
I'd like restructure our codebase a little as it feels a bit scattered
to me, in particular I'd like to move
src/* = src/main/* (except for site)
tests = src/tests
examples = src/examples
extensions = src/extensions
and I'd like to modify the build files so that assemblies and all
Hi,
I don't think I've ever built the extension, in fact I wouldn't even
know what they contain without looking it up. The situation is similar
for the examples.
We'd need to modernize them in some way and maybe add new examples like
for the new extensions methods API.
This could be a nice
On 2013-10-25, Dominik Psenner wrote:
* the next release will be 1.3.0 and require .NET 2.0 or better
I.e. we remove support for .NET 1.0 and 1.1, Compact Framework 1.0,
Mono 2.0, SSCLI and CLI 1.0 frameworks
That's even worth a +2! ;-)
* the main assembly will get a new name like
401 - 500 of 895 matches
Mail list logo
