On Oct 11, 2011, at 4:02 AM, Stefan Bodewig wrote:
> On 2011-10-11, Curt Arnold wrote:
>
>> both bin/2.0/release/log4net.dll and bin/3.5/release/log4net.dll
>> describe themselves as Apache log4net for the .NET Framework
>> 2.0. Everybody else has the expected
More observations:
oldkey.zip
LICENSE and NOTICE are present, but with Unix style linefeeds.
both bin/2.0/release/log4net.dll and bin/3.5/release/log4net.dll describe
themselves as Apache log4net for the .NET Framework 2.0. Everybody else has the
expected application description.
log4net-sdk-
Observations:
GPG keys check out
comparing the source zip with the SVN tag, the following items are not in the
source zip:
doap_log4net.rdf (DOAP file placed here for convenience)
src/site/fml (empty directory)
src/site/resources/js (empty directory)
tests/lib/prerequisites.txt (note on prerequ
Totally packed weekend. Will try to free up some time tomorrow.
Has anyone compared how the new log4net.dll performs with the previous
release's test suite?
On Oct 7, 2011, at 6:54 AM, Stefan Bodewig wrote:
> On 2011-10-06, Stefan Bodewig wrote:
>
>> Votes, please. This vote will close in 7
On Sep 23, 2011, at 2:07 AM, Dominik Psenner wrote:
>
> I've so far found this:
>
> http://logging.apache.org/log4j/companions/extras/apidocs/org/apache/log4j/r
> olling/package-tree.html
>
> Despite the fact that it is there in "extras", you're suggesting that it was
> abandoned? Why?
>
The
Take a look at org.apache.log4j.rolling.RollingFileAppender which has pluggable
rolling and file naming strategies.
http://logging.apache.org/log4j/1.2/apidocs/index.html
For a little ancient history, log4j 1.2 has two classes named
RollingFileAppender, the original in org.apache.log4j and a ne
The rolling file appenders are the single greatest cause of recurring problems
in log4j and all those problems have been inherited by log4net.
I don't think that the rolling file appenders are fixable. Any approach that
involves systematic renaming for files is not going to be robust. Even a si
[
https://issues.apache.org/jira/browse/LOG4NET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094288#comment-13094288
]
Curt Arnold commented on LOG4NET-290:
-
The JavaDoc for LogMF is
[
https://issues.apache.org/jira/browse/LOG4NET-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094285#comment-13094285
]
Curt Arnold commented on LOG4NET-290:
-
It looks the like original code was
The SVN commits have been redirected and will no longer go to the -dev lists
(or gene...@logging.apache.org for Chainsaw).
On Aug 25, 2011, at 10:49 PM, Curt Arnold wrote:
> The comm...@logging.apache.org mailing list is now accepting subscription
> requests at commits-
[
https://issues.apache.org/jira/browse/LOG4NET-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093421#comment-13093421
]
Curt Arnold commented on LOG4NET-306:
-
FYI: log4j handles this by providi
The comm...@logging.apache.org mailing list is now accepting subscription
requests at commits-subscr...@logging.apache.org. The current plan is to
redirect all SVN commit messages from logging services projects to
comm...@logging.apache.org and to discontinue any commit message logging to
log4j
Incorporate a compatibility checker to the build
Key: LOG4NET-308
URL: https://issues.apache.org/jira/browse/LOG4NET-308
Project: Log4net
Issue Type: Task
Reporter: Curt Arnold
Please welcome Stefan Bodewig to the Logging Project Management Committee
(PMC). Stefan is an Apache Software Foundation member, PMC Chair for Gump, and
member of the Ant, Commons, Incubator, and Jakarta PMCs.
Stefan has volunteered to assist in a release march for log4net and is expected
to be
[
https://issues.apache.org/jira/browse/LOG4NET-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085066#comment-13085066
]
Curt Arnold commented on LOG4NET-108:
-
The patch file did not apply cleanly fo
I currently have commit rights and I'm working the process right now to add
additional help though the process takes a certain amount of time. Expect an
announcement on Wednesday.
Code development at the ASF should be done in the open and not in a private
branch that unveiled to the community (
On Aug 10, 2011, at 10:38 AM, Stefan Bodewig wrote:
> I'd propose to not keep the signing key of future releases secret but
> simply keep the full keypair inside the source tree.
>
> Stefan
I'm fine with that as long as it is a different key than that which signed the
earlier releases which had
By the way, no need to apologize. The ASF is an educational foundation and
community which happens to produce software.
On Aug 9, 2011, at 6:15 PM, Jim Scott wrote:
>
>
> On 8/8/2011 8:34 PM, Curt Arnold wrote:
>> I'd be happy to perform the release build or reencryp
Good to have both of you here.
Hopefully the content under "Contribute back to the community" at
http://www.apache.org/foundation/getinvolved.html can get you started.
Write access to the ASF source code repository is granted by a process that
requires some history of contribution to a project
I wrote this message last night in response to the is log4net in a cul-du-sac
thread, but it got bounced due to a spam guard which I've hopefully satisfied
this time. The strong naming key that has been used to sign log4net releases
has been encrypted and can be decrypted using the private key
Components: Documentation
Reporter: Curt Arnold
All Apache projects are to bring their sites into conformance with the Apache
Project Branding requirements (http://www.apache.org/foundation/marks/pmcs) by
Q1 2011.
--
This message is automatically generated by JIRA.
-
You can reply
Can't make ApacheCon this week in New Orleans? You can still watch all
the keynotes, Apache 101 sessions, and system administration track in
live video streams:
http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann
Keynotes and the Apache 101 lunchtime sessions are free; the full
[
https://issues.apache.org/jira/browse/LOG4NET-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593489#action_12593489
]
Curt Arnold commented on LOG4NET-149:
-
Updated link from cvs.apache.or
[
https://issues.apache.org/jira/browse/LOG4NET-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593487#action_12593487
]
Curt Arnold commented on LOG4NET-150:
-
Duplicate of LOG4NET-149.
> Cannot d
All PMC Chairs have been requested to report on the use of
cryptography within their projects in their quarterly board reports
(which are due shortly).
I did a quick scan on the log4net for "crypto" and found mentions in
three places:
cs/src/AssemblyInfo.cs
src/AssemblyInfo.cs
Describes p
[
https://issues.apache.org/jira/browse/LOG4NET-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556327#action_12556327
]
Curt Arnold commented on LOG4NET-116:
-
Many ISP SMTP servers are starting to req
[
https://issues.apache.org/jira/browse/LOG4NET-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556325#action_12556325
]
Curt Arnold commented on LOG4NET-8:
---
This should be coordinated with the other log
On Jan 1, 2008, at 2:12 AM, <[EMAIL PROTECTED]> wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4net has an issue aff
A release vote for log4j-1.2.15 and log4j-extras-1.0 is going on
[EMAIL PROTECTED] and log4j-dev at the moment. As part of the release
process, the LS web site would be updated to the staged content at
https://svn.apache.org/repos/asf/logging/site/trunk/docs/index.html.
Looks like there a
On Aug 2, 2007, at 1:16 AM, Cliff Burger wrote:
A file is not a good target for multiple users or threads, unless
you have some type of service in front of it. If you do, you have a
database server.
To be rhetorical: Is building this type of architecture (basically,
the IO handling of
There has been a thread on log4php-dev (http://marc.info/?l=log4php-
dev&m=118520958818276&w=2) that I'd like to get an opinion from the
log4net developers. Basically, the user wishes to allow multiple
user accounts to be able to write to the same log file and they are
being prevented since
On Jul 26, 2007, at 2:18 AM, Curt Arnold (JIRA) wrote:
Migrate web content generation of Maven 2.0
---
Should have mentioned the generated content from all the now-
Mavenized LS projects can be viewed at http://svn.apache.org/repos/
asf/logging
Reporter: Curt Arnold
The other LS projects have been migrating to Maven 2.0 for documentation
generation and deployment, packaging and, for the Java projects, build and
dependency management. Migrating log4net would complete the migration and
would allow consistency between the web content of the
[
https://issues.apache.org/jira/browse/LOG4NET-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515131
]
Curt Arnold commented on LOG4NET-2:
---
This one also affects log4j and logcxx (and likely log4php). log4j 2.0 will
vmgump recently was moved and in the process we've got log4net to
build mono 1.0 and 2.0 debug builds on Gump (http://vmgump.apache.org/
gump/public/logging-log4net/logging-log4net/gump_work/build_logging-
log4net_logging-log4net.html). From now on out, if you make a code
change that breaks
On Feb 27, 2007, at 3:44 AM, Nicko Cadell wrote:
Curt,
I think that the Apache license notice is already being emitted
into the
generated documents, your change adds it in twice.
Unless there is something wrong with the current source for
http://logging.apache.org/log4net/ then I think we s
[
https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold updated LOG4NET-114:
Attachment: tests.log
Changes fixed all of the tests that displayed \n\r, but causes some of the
[
https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold updated LOG4NET-114:
Attachment: tests.log
Test results from Mono 1.2.3.1 on Mac OS/X. In addition to
[
https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474356
]
Curt Arnold commented on LOG4NET-114:
-
That could be an issue, but that was not the issue that I was running up
[
https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474285
]
Curt Arnold commented on LOG4NET-114:
-
Rev 509338 will allow the unit tests to run (but fail) on Mono 2.0
Unit tests only support .NET 1.0
Key: LOG4NET-114
URL: https://issues.apache.org/jira/browse/LOG4NET-114
Project: Log4net
Issue Type: Bug
Components: Other
Reporter: Curt Arnold
tests
On Feb 17, 2007, at 3:05 PM, Nicko Cadell wrote:
1. Build should be reproducible (other than timestamps and
other trivia)
I'm not sure how you are handling strong naming in your
releases. If you have a signing key, we may want to find a
way to securely share the key. Perhaps have it gpg e
I think it would be good in relatively short order to do a post-
graduation release. Don't know where things are in the development
cycle, so I'll defer to everybody else on the actual timing.
There are a few things that will need to be checked on the release.
I'm rattling these off the to
FYI
Begin forwarded message:
From: Curt Arnold <[EMAIL PROTECTED]>
Date: February 16, 2007 9:36:43 PM CST
To: general@incubator.apache.org
Subject: [VOTE][RESULT] log4net graduation
Reply-To: general@incubator.apache.org
On Feb 13, 2007, at 5:15 PM, Curt Arnold wrote:
The log4n
On Feb 14, 2007, at 2:55 PM, Gert Driesen wrote:
+1
Good to see you back. The vote is now at [EMAIL PROTECTED] and seems
to be progressing to a favorable conclusion. The primary issue was
whether the project satisfied the survivability issue and
particularly the 3 independent committer
Sorry about that. Nicko Cadell (PMC) +1
I have called for a vote on [EMAIL PROTECTED] Anyone who is
interested in following the discussion should subscribe by sending an
email to [EMAIL PROTECTED] The archives are
available at http://mail-archives.apache.org/mod_mbox/incubator-
general/
On Feb 9, 2007, at 12:49 PM, Curt Arnold wrote:
There was a previous discussions log4net-dev on 2006-09-18 http://
marc.theaimsgroup.com/?l=log4net-dev&m=115861418117968&w=2 and a
thread on [EMAIL PROTECTED] on 2007-02-08 (http://www.mail-
archive.com/general@incubator.apache.org/
On Feb 11, 2007, at 3:48 PM, [EMAIL PROTECTED] wrote:
Check of project name for trademark issues
Google search for log4net exclusively came up with ASF
related links (or the earlier SourceForge log4net which
indicates code has moved to
ASF) with the exception of log4net.net which appears to
http://incubator.apache.org/incubation/Incubation_Policy.html#Minimum
+Exit+Requirements
These requirements were previously considered in [EMAIL PROTECTED] in
2004-11-25, see http://marc.theaimsgroup.com/?l=apache-logging-
general&m=110141756729362&w=2 and following.
This section describ
[
https://issues.apache.org/jira/browse/LOG4NET-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold resolved LOG4NET-111.
-
Resolution: Fixed
Committed the DOAP file in the root directory. If there are no objections in
[
https://issues.apache.org/jira/browse/LOG4NET-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold updated LOG4NET-111:
Attachment: doap_log4net.rdf
Description of a project file (DOAP) for log4net. Similar to
Reporter: Curt Arnold
projects.apache.org is a catalog of Apache projects that is generated from
project supplied metadata. This issue requests adding a metadata file to the
log4net repository to allow log4net to appear in projects.apache.org alongside
log4j and log4cxx.
--
This message is
There was a previous discussions log4net-dev on 2006-09-18 http://
marc.theaimsgroup.com/?l=log4net-dev&m=115861418117968&w=2 and a
thread on [EMAIL PROTECTED] on 2007-02-08 (http://www.mail-
archive.com/general@incubator.apache.org/msg12442.html) regarding
log4net graduating from the incubat
ASF board meets on November 15th and a quarterly board report is
due. I'm sorry to have not been following log4net very much
recently, so if you have anything that you think should be reported
to the board, please reply and I'll add it to the report.
smime.p7s
Description: S/MIME cryptograp
Could someone summarize the unfulfilled criteria that is preventing
log4net from exiting the incubator? Any thoughts on a plan to reach
those criteria. I haven't been following log4net closely, but it
seems to be mature and accepted enough that it should graduate
sometime soon.
One thin
Sorry to leave you out of my once yearly cross-post.
Begin forwarded message:
From: Curt Arnold <[EMAIL PROTECTED]>
Date: September 14, 2006 12:47:42 PM CDT
To: Logging General
Cc: Log4J Developers List , Log4CXX
Dev , Log4J Users List [EMAIL PROTECTED]>, Log4CXX User [EMAIL
On Mar 24, 2006, at 5:49 AM, Nicko Cadell wrote:
It looks like the log4j sandbox and the .net framework agree on the
number of override params, 3. This gives signatures like:
void DebugFormat(string format);
void DebugFormat(string format, object arg0);
void DebugFormat(string format, object a
On Mar 19, 2006, at 1:40 AM, Jaroslaw Kowalski wrote:
Small hint from NLog developer:
Why don't you pass the raw message with parameter placeholders,
format arguments and IFormatProvider down to the logging engine and
defer calling the actual String.Format to as late as possible?
This wa
I'm sure the timing sucks, but since the scuttling of the 1.2.10
release involves formatting log messages and I have recently been
doing some things in the log4j sandbox, I thought that I would bring
that work to your attention. The project can be checked out from
http://svn.apache.org/rep
59 matches
Mail list logo
