headers
david olszewski (JIRA | 7 Jul 2007 23:50
Picon
Favicon

[jira] Created: (LOG4NET-116) allow smtp to ssl authenticate and with certificates.

allow smtp to ssl authenticate and with certificates.
-----------------------------------------------------

                 Key: LOG4NET-116
                 URL: https://issues.apache.org/jira/browse/LOG4NET-116
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders
         Environment: .net 2.0
windows
            Reporter: david olszewski

It would be fantastic if more of the SMTP feature of .net 2.0 would be allowed such as 
SSL authentication and with certificates.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 8 comments |
headers
Curt Arnold | 20 Jul 2007 08:07
Picon
Favicon

log4net on Gump, Maven generated docs and standard directory layout

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 the build, you should receive an automated nag email.

I've been working on migrating the overall Logging Services and log4j  
web content to use Maven 2.0 for build and deployment.  I expect to  
migrate log4cxx over tomorrow.  I'd like to take a shot on log4net  
thereafter and wanted to give you some advance notice.   I'd envision  
Maven handling the documentation and packaging and deferring to Nant  
actually build the assemblies.

Maven has a standard directory layout (http://maven.apache.org/guides/ 
introduction/introduction-to-the-standard-directory-layout.html).  It  
would not be essential to migrate to the standard layout, but it  
would make things easier and more consistent with the other  
projects.  To move to the standard layout:

doc is removed from SVN
examples moves to src/examples
extensions moves to src/extension
src moves to src/main/cs
tests/src moves to src/test/cs
xdocs moves to src/site/xdoc

The layout of examples and extensions seemed pretty complicated, but  
don't think it is essential to unwind them.  doc can be removed since  
Maven would build web content into target/site and site deployment  
would commit the generated content into http://svn.apache.org/repos/
(Continue reading)

Permalink | Reply | 1 comment |
headers
nicko | 20 Jul 2007 14:44
Picon
Favicon

RE: log4net on Gump, Maven generated docs and standard directory layout

Curt,

I think it would be a good move to bring the projects into line on the
Maven platform. The build script for log4net is rather complex and the
directory structure of the src, extensions, and examples folder is
rather tied into the way the build works. I would prefer not to have to
change the build scripts.

Let us know how you get on.

Cheers,
Nicko

------------
Nicko Cadell
log4net development
http://logging.apache.org/log4net

> -----Original Message-----
> From: Curt Arnold [mailto:carnold <at> apache.org]
> Sent: 20 July 2007 07:08
> To: Log4NET Dev
> Subject: log4net on Gump, Maven generated docs and standard directory
layout
> 
> 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 the build, you should receive an automated nag
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jerry Wang | 23 Jul 2007 04:31
Picon

XSD Schema Files of log4net configuration file for vs2005.

Dear All great log4net developer,

log4net is a great framework for logging. When I use log4net from
vs2005, I need a xsd schema file for vs2005 to provide intellisense
and xml validation for log4net. I've googled, but I found none. So I
decide to write my own. I think this file should include in log4net
release package, so I've attached my xsd schema file for your
reference.
Attachment (log4net.xsd): application/xml, 3246 bytes
Permalink | Reply | 0 comments |
headers
Eugene Lim | 23 Jul 2007 04:50

RE: XSD Schema Files of log4net configuration file for vs2005.

Love it.

Eugene

-----Original Message-----
From: Jerry Wang [mailto:didasoft <at> gmail.com] 
Sent: Monday, July 23, 2007 10:31 AM
To: log4net-dev <at> logging.apache.org
Subject: XSD Schema Files of log4net configuration file for vs2005.

Dear All great log4net developer,

log4net is a great framework for logging. When I use log4net from
vs2005, I need a xsd schema file for vs2005 to provide intellisense
and xml validation for log4net. I've googled, but I found none. So I
decide to write my own. I think this file should include in log4net
release package, so I've attached my xsd schema file for your
reference.
Permalink | Reply | 0 comments |
headers
Curt Arnold (JIRA | 25 Jul 2007 03:11
Picon
Favicon

[jira] Commented: (LOG4NET-2) Configurator should report errors


    [
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 likely revisit the whole
configuration space and one possible approach is to collaborate on a common redesign and then push it to
all the frameworks.  On a tangental issue, I did some exploratory work on a strictxml configuration
dialect (where a validating parser or XML editor would be much more likely to identify configuration
errors) a few years ago in the sandbox.

My thinking on log4j 2.0 is to first design for configuration by Java Management Extension (JMX) and then an
existing configuration framework (there are a couple already in ASF).  Support for the existing log4j
configuration formats could be provided by XSLT transforming the configuration files into the "new"
configuration language and then having the existing framework process it.  configurationAndWatch is
addictive but problematic and a JMX approach for run-time modification of configuration would be much cleaner.

> Configurator should report errors
> ---------------------------------
>
>                 Key: LOG4NET-2
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-2
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.9
>         Environment: From sourceforege - Tor Hovland - torhovl
(Continue reading)

Permalink | Reply | 0 comments |
headers
Curt Arnold (JIRA | 26 Jul 2007 09:18
Picon
Favicon

[jira] Created: (LOG4NET-117) Migrate web content generation of Maven 2.0

Migrate web content generation of Maven 2.0
-------------------------------------------

                 Key: LOG4NET-117
                 URL: https://issues.apache.org/jira/browse/LOG4NET-117
             Project: Log4net
          Issue Type: Task
          Components: Builds
            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 various projects.

The initial commit overlays the existing source code struction with fragments of the Maven Standard
Directory Layout,.  The following directories are added:

src/assembly - release packaging info, includes assembly.bin borrowed from another project.

src/changes - project change list.  Includes sample changes.xml.  log4cxx has an XSLT transform that can
generate changes.xml from a downloaded JIRA issue list.  Used to generate change-report.html.

src/site - documentation source files, site.xml contains navigation and layout details for all
generated pages
src/site/apt - web content in Maven's APT (almost plain text) format
src/site/resources - static content copied over without processing
src/site/xdoc - XDoc content, I copied the existing xdocs content here, but deleted a few no longer needed pages

The existing C# code in src should be relocated to src/main/cs and the build and project files
appropriately changed.  For extra credit, the following relocations would bring the layout closer to a
(Continue reading)

Permalink | Reply | 1 comment |
headers
carnold | 26 Jul 2007 09:19
Picon
Favicon

svn commit: r559731 - in /logging/log4net/trunk: ./ src/assembly/ src/changes/ src/site/ src/site/apt/ src/site/fml/ src/site/resources/ src/site/xdoc/

Author: carnold
Date: Thu Jul 26 00:19:21 2007
New Revision: 559731

URL: http://svn.apache.org/viewvc?view=rev&rev=559731
Log:
LOG4NET-117: Initial Maven 2.0 stuff

Added:
    logging/log4net/trunk/pom.xml
      - copied, changed from r559686, logging/log4cxx/trunk/pom.xml
    logging/log4net/trunk/src/assembly/
      - copied from r559678, logging/log4j/branches/v1_2-branch/src/assembly/
    logging/log4net/trunk/src/changes/
    logging/log4net/trunk/src/changes/changes.xml
    logging/log4net/trunk/src/site/
    logging/log4net/trunk/src/site/apt/
    logging/log4net/trunk/src/site/apt/download.apt
      - copied, changed from r559686, logging/log4cxx/trunk/src/site/apt/download.apt
    logging/log4net/trunk/src/site/apt/roadmap.apt
      - copied, changed from r559686, logging/log4cxx/trunk/src/site/apt/roadmap.apt
    logging/log4net/trunk/src/site/fml/
    logging/log4net/trunk/src/site/fml/faq.fml
    logging/log4net/trunk/src/site/resources/
      - copied from r559678, logging/log4j/branches/v1_2-branch/src/site/resources/
    logging/log4net/trunk/src/site/site.xml
      - copied, changed from r559678, logging/log4j/branches/v1_2-branch/src/site/site.xml
    logging/log4net/trunk/src/site/xdoc/
      - copied from r559678, logging/log4net/trunk/xdocs/src/
Removed:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Curt Arnold | 26 Jul 2007 09:26
Picon
Favicon

Re: [jira] Created: (LOG4NET-117) Migrate web content generation of Maven 2.0


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/site/trunk/docs/index.html.  The link to log4net needs to  
be fixed (it will get you a directory listing from which you need to  
select index.html).  But now close to having the new web layout in  
place, we can go back and start making releases.
Permalink | Reply | 0 comments |
headers
Patrick Gautschi (JIRA | 29 Jul 2007 08:26
Picon
Favicon

[jira] Created: (LOG4NET-118) RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work

RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work
---------------------------------------------------------------------------------

                 Key: LOG4NET-118
                 URL: https://issues.apache.org/jira/browse/LOG4NET-118
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: Windows 2003 / Microsoft .NET Framework 2.0
            Reporter: Patrick Gautschi
            Priority: Minor

When using the an appender configuration like

    <appender name="InfoFile" type="log4net.Appender.RollingFileAppender">
      <file value="info.log" />
      <appendToFile value="false" />
      <encoding value="utf-8" />
      <countDirection value="1" />
      <maximumFileSize value="1MB" />
      <maxSizeRollBackups value="3" />
      <staticLogFileName value="false" />
      <rollingStyle value="Size" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%utcdate{yyyy-MM-dd HH:mm:ss.ff}Z [%thread] %-5level %logger -
%message%newline" />
      </layout>
    </appender>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane