Roy Chastain | 2 Nov 15:57 2011

Survey about the direction of log4Net

This email is cross-posted to both the Dev and User lists because of the small chance that someone on the Dev list is not subscribed to the User list.

 

A survey about your use of log4Net has been created in an effort to revitalize the log4Net project and to determine the needs of the log4Net community.  This is a short 7 yes/no question survey with one optional general comment question.  The entire survey process should take less than five minutes.  Please take time to respond to this survey.

 

The survey is hosted on a site which requires user authentication.  Please use the credentials below when prompted by the site.

UserId log4Net <at> sohotech.biz

Password l0g4N#t

 

Please start the survey by clicking

http://www.sohotech.biz/Lists/log4Net%20Survey/overview.aspx.

 

Once the page displays, you may respond to the survey by clicking Respond to this Survey in the upper left corner of the white portion of the page.

 

Thank you for participating in this survey.

 

 

Roy Chastain

 

 

 

 

Picon

[jira] [Updated] (LOG4NET-292) Managed ColoredConsoleAppender for .NET2/Mono.


     [
https://issues.apache.org/jira/browse/LOG4NET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-292:
-----------------------------------

    Affects Version/s:     (was: 1.2.10)
                       1.2.11
        Fix Version/s:     (was: 1.2 Maintenance Release)
                       1.2.12

I've renamed the class and made it compile on .NET 2.0 (automatic Has*Color properties in LevelColors). 
Other than that the code is in with svn revision 1197200.

Do you think you could provide a small documentation snippet for
http://logging.apache.org/log4net/release/config-examples.html which is based on
https://svn.apache.org/repos/asf/logging/log4net/trunk/src/site/xdoc/release/config-examples.xml ?

> Managed ColoredConsoleAppender for .NET2/Mono.
> ----------------------------------------------
>
>                 Key: LOG4NET-292
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-292
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Pavlos Touboulidis
>            Priority: Minor
>             Fix For: 1.2.12
>
>         Attachments: ColoredConsoleAppender2.cs
>
>
> The original ColoredConsoleAppender was written before the .NET framework (and Mono) had built-in
support for console colors so it was written using Win32 API calls. The AnsiColorTerminalAppender,
while it works, isn't understood by the Windows command prompt so there's no console appender that works
on both environments.
> I'm attaching a replacement for both classes that uses the new (.NET 2) console colors and works on both
platforms. It is based on the existing ColoredConsoleAppender. The color mapping values are not
compatible with the previous version since this one uses the standard .NET 2 ConsoleColor enumeration values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

bodewig | 4 Nov 01:13 2011
Picon

[GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net) failed

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 general <at> gump.apache.org.

Project logging-log4net has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 67 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4net :  Logging framework for .NET.

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason build failed

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/gump_work/build_logging-log4net_logging-log4net.html
Work Name: build_logging-log4net_logging-log4net (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: nant -D:java.awt.headless=true -D:build.sysclasspath=only
-D:gump.merge=/srv/gump/public/gump/work/merge.xml -buildfile:log4net.build 
[Working Directory: /srv/gump/public/workspace/logging-log4net]
---------------------------------------------

check-sdkdoc-dir:

check-sdkdoc-debug:

check-current-build-config:

check-build-debug:

check-build-defines:

set-mono-1.0-runtime-configuration:

 [property] Target framework changed to "Mono 1.0 Profile".

check-log4net-basedir:

check-current-bin-dir:

    [mkdir] Creating directory '/srv/gump/public/workspace/logging-log4net/bin/mono/1.0/debug'.

clean-current-bin-dir:

     [echo] Cleaning the bin/mono/1.0/debug binaries directory.
   [delete] Deleting directory '/srv/gump/public/workspace/logging-log4net/bin/mono/1.0/debug'.
    [mkdir] Creating directory '/srv/gump/public/workspace/logging-log4net/bin/mono/1.0/debug'.

compile-mono-1.0:

      [csc] Compiling 219 files to '/srv/gump/public/workspace/logging-log4net/bin/mono/1.0/debug/log4net.dll'.
      [csc]
/srv/gump/public/workspace/logging-log4net/src/Appender/ManagedColoredConsoleAppender.cs(304,33):
error CS0246: The type or namespace name `ConsoleColor' could not be found. Are you missing a using
directive or an assembly reference?
      [csc]
/srv/gump/public/workspace/logging-log4net/src/Appender/ManagedColoredConsoleAppender.cs(328,33):
error CS0246: The type or namespace name `ConsoleColor' could not be found. Are you missing a using
directive or an assembly reference?
      [csc]
/srv/gump/public/workspace/logging-log4net/src/Appender/ManagedColoredConsoleAppender.cs(297,32):
error CS0246: The type or namespace name `ConsoleColor' could not be found. Are you missing a using
directive or an assembly reference?
      [csc]
/srv/gump/public/workspace/logging-log4net/src/Appender/ManagedColoredConsoleAppender.cs(321,32):
error CS0246: The type or namespace name `ConsoleColor' could not be found. Are you missing a using
directive or an assembly reference?
      [csc] Compilation failed: 4 error(s), 0 warnings

BUILD FAILED - 0 non-fatal error(s), 4 warning(s)

/srv/gump/public/workspace/logging-log4net/log4net.build(994,6):
External Program Failed: /usr/lib/mono/1.0/mcs.exe (return code was 1)

Total time: 2.3 seconds.

---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/atom.xml

============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 10000004112011, vmgump.apache.org:vmgump:10000004112011
Gump E-mail Identifier (unique within run) #2.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

Picon

[jira] [Resolved] (LOG4NET-223) [PATCH] Improve AnsiColorTerminalAppender to support marking colors as Light


     [
https://issues.apache.org/jira/browse/LOG4NET-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved LOG4NET-223.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.2 Maintenance Release)
                   1.2.12

patch applied with svn revision  1197625

Thanks!

> [PATCH] Improve AnsiColorTerminalAppender to support marking colors as Light
> ----------------------------------------------------------------------------
>
>                 Key: LOG4NET-223
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-223
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Tested on Ubuntu Karmic, with log4net 1.2.10, should work on all Unix environments that
speak VT100.
>            Reporter: Bojan
>            Priority: Trivial
>             Fix For: 1.2.12
>
>         Attachments: light-adjustment.patch
>
>
> The attached patch adds the ability to mark AnsiColors as Light using AnsiAttribute. This fixes a minor
glitch in AnsiColorTerminalAppender that would cause AnsiColorTerminalAppender to output a grey-ish
color instead of white when BackColor was set to AnsiColor.White by allowing the user to set the proper
option of AnsiAttribute.Light and AnsiColor.White, rather than setting BackColor manually to 67 (60
for the light adjustment, 7 for white), and allows more color expressivity.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon

[jira] [Updated] (LOG4NET-227) create a more directory when log files.


     [
https://issues.apache.org/jira/browse/LOG4NET-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-227:
-----------------------------------

    Component/s:     (was: Builds)
                 Appenders

> create a more directory when log files.
> ---------------------------------------
>
>                 Key: LOG4NET-227
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-227
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: .net
>            Reporter: ljm
>            Priority: Critical
>             Fix For: 1.2 Maintenance Release
>
>
> Something unpredicted happened When using log4.net. 
> As I understood during one hour we should have just one log file named for example '15.log' if translation
requests come during this hour. But in my case new folder named 15.log20090811 has been created in the
\\scratchy\sysdev$\qa\SoapLogs\WebService1\20090811 and new file 15.log in it.
> Do you have an idea why existing 15.log file wasn't updated with that information?
> The log4.net appender configuration as follows:
> <appender name="FileAppender" type="log4net.Appender.RollingFileAppender">
>       <file value="\\scratchy\sysdev$\qa\SoapLogs\WebService1\" />
>       <appendToFile value="true" />
>       <rollingStyle value="Composite" />
>       <datePattern value="yyyyMMdd&quot;\\&quot;HH&quot;.log&quot;" />
>       <lockingModel type="log4net.Appender.RollingFileAppender+MinimalLock"/>
>       <StaticLogFileName value="false" />
>       <layout type="log4net.Layout.PatternLayout">
>         <conversionPattern value="-- %date [%thread] %-5level %logger --%newline%message%newline" />
>       </layout>
>     </appender>
> Thanks.
> Liu jianming.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon

[jira] [Commented] (LOG4NET-227) create a more directory when log files.


    [
https://issues.apache.org/jira/browse/LOG4NET-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145577#comment-13145577
] 

Stefan Bodewig commented on LOG4NET-227:
----------------------------------------

rollingStyle of Composite means you are rolling based on date and on size - you really should be setting the
maximumFileSize  as well if this is intended.

It looks as if you are trying to plug a dynamic directory name into the date pattern, this simply isn't
supported properly.  Several parts of RollingFileAppender expect the name of the file (without any
leading directories) to match the pattern given in datePattern.

> create a more directory when log files.
> ---------------------------------------
>
>                 Key: LOG4NET-227
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-227
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: .net
>            Reporter: ljm
>            Priority: Critical
>             Fix For: 1.2 Maintenance Release
>
>
> Something unpredicted happened When using log4.net. 
> As I understood during one hour we should have just one log file named for example '15.log' if translation
requests come during this hour. But in my case new folder named 15.log20090811 has been created in the
\\scratchy\sysdev$\qa\SoapLogs\WebService1\20090811 and new file 15.log in it.
> Do you have an idea why existing 15.log file wasn't updated with that information?
> The log4.net appender configuration as follows:
> <appender name="FileAppender" type="log4net.Appender.RollingFileAppender">
>       <file value="\\scratchy\sysdev$\qa\SoapLogs\WebService1\" />
>       <appendToFile value="true" />
>       <rollingStyle value="Composite" />
>       <datePattern value="yyyyMMdd&quot;\\&quot;HH&quot;.log&quot;" />
>       <lockingModel type="log4net.Appender.RollingFileAppender+MinimalLock"/>
>       <StaticLogFileName value="false" />
>       <layout type="log4net.Layout.PatternLayout">
>         <conversionPattern value="-- %date [%thread] %-5level %logger --%newline%message%newline" />
>       </layout>
>     </appender>
> Thanks.
> Liu jianming.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon

[jira] [Updated] (LOG4NET-202) AdoNetAppenderParameter.Size Property is not optional


     [
https://issues.apache.org/jira/browse/LOG4NET-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-202:
-----------------------------------

    Affects Version/s: 1.2.11
        Fix Version/s:     (was: 1.2 Maintenance Release)
                       1.2.12

I have changed the documentation in svn to recommend using -1 explicitly but it would if anybody could
confirm this actually works before I close the issue (and update the site).

> AdoNetAppenderParameter.Size Property is not optional
> -----------------------------------------------------
>
>                 Key: LOG4NET-202
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-202
>             Project: Log4net
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.2.10, 1.2.11
>         Environment: Windows Server 2008, .NET 3.5 SP1, SQL Server 2008
>            Reporter: Richard Dingwall
>             Fix For: 1.2.12
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The AdoNetAppenderParameter.Size page
(http://logging.apache.org/log4net/release/sdk/log4net.Appender.AdoNetAppenderParameter.Size.html)
says "This property is optional. If not specified the ADO.NET provider will attempt to infer the size from
the value."
> However, I just got the following exception in the log4net internal debug trace, with the following
parameter (maps to a VARCHAR(MAX)):
> <parameter>
>       <parameterName value=" <at> exception" />
>       <dbType value="String" />
>       <layout type="log4net.Layout.ExceptionLayout" />
> </parameter>
> log4net:ERROR [AdoNetAppender] Could not prepare database command [INSERT INTO ....]
> System.InvalidOperationException: SqlCommand.Prepare method requires all variable length
parameters to have an explicitly set non-zero Size.
>    at System.Data.SqlClient.SqlParameter.Prepare(SqlCommand cmd)
>    at System.Data.SqlClient.SqlCommand.Prepare()
>    at log4net.Appender.AdoNetAppender.InitializeDatabaseCommand()
> This would suggest the Size parameter cannot be null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon

[jira] [Updated] (LOG4NET-292) Managed ColoredConsoleAppender for .NET2/Mono.


     [
https://issues.apache.org/jira/browse/LOG4NET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavlos Touboulidis updated LOG4NET-292:
---------------------------------------

    Attachment: config-examples.patch

Indeed, ManagedColoredConsoleAppender makes more sense. Good call on the automatic properties, forgot
all about them. Thanks.

I've attached a patch for the configuration example. Is it OK?

> Managed ColoredConsoleAppender for .NET2/Mono.
> ----------------------------------------------
>
>                 Key: LOG4NET-292
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-292
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Pavlos Touboulidis
>            Priority: Minor
>             Fix For: 1.2.12
>
>         Attachments: ColoredConsoleAppender2.cs, config-examples.patch
>
>
> The original ColoredConsoleAppender was written before the .NET framework (and Mono) had built-in
support for console colors so it was written using Win32 API calls. The AnsiColorTerminalAppender,
while it works, isn't understood by the Windows command prompt so there's no console appender that works
on both environments.
> I'm attaching a replacement for both classes that uses the new (.NET 2) console colors and works on both
platforms. It is based on the existing ColoredConsoleAppender. The color mapping values are not
compatible with the previous version since this one uses the standard .NET 2 ConsoleColor enumeration values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Picon

[jira] [Resolved] (LOG4NET-292) Managed ColoredConsoleAppender for .NET2/Mono.


     [
https://issues.apache.org/jira/browse/LOG4NET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved LOG4NET-292.
------------------------------------

    Resolution: Fixed

Thanks!

Patch applied as svn revision 1203145

> Managed ColoredConsoleAppender for .NET2/Mono.
> ----------------------------------------------
>
>                 Key: LOG4NET-292
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-292
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Pavlos Touboulidis
>            Priority: Minor
>             Fix For: 1.2.12
>
>         Attachments: ColoredConsoleAppender2.cs, config-examples.patch
>
>
> The original ColoredConsoleAppender was written before the .NET framework (and Mono) had built-in
support for console colors so it was written using Win32 API calls. The AnsiColorTerminalAppender,
while it works, isn't understood by the Windows command prompt so there's no console appender that works
on both environments.
> I'm attaching a replacement for both classes that uses the new (.NET 2) console colors and works on both
platforms. It is based on the existing ColoredConsoleAppender. The color mapping values are not
compatible with the previous version since this one uses the standard .NET 2 ConsoleColor enumeration values.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Roy Chastain | 18 Nov 14:20 2011

Survey about the direction of log4Net - Update

This email is cross-posted to both the Dev and User lists because of the small chance that someone on the Dev list is not subscribed to the User list.

 

I would like to share some of the responses from the 24 responders to the survey.

            Only one respondent has indicated a requirement for framework 1.0 or 1.1; however, seven require MONO.

            Zero responders have indicated a need for the 1.0/1.1 Compact Framework.  I know that is welcome news to the people that do the builds.

            There is a lot of interest in versions targeted to Silverlight.

 

If you have not already responded, please take time to respond to this survey.  Do not let 24 people speak for the log4Net user community.

 

The survey is hosted on a site which requires user authentication.  Please use the credentials below when prompted by the site.

UserId log4Net <at> sohotech.biz

Password l0g4N#t

 

Please start the survey by clicking

http://www.sohotech.biz/Lists/log4Net%20Survey/overview.aspx.

 

Once the page displays, you may respond to the survey by clicking Respond to this Survey in the upper left corner of the white portion of the page.

 

Thank you for participating in this survey.

 

 

Roy Chastain

 

 

 

 


Gmane