gmane.comp.apache.logging

log4cxx client server program

Soumik Sur — 2013-06-16T15:10:27

Hi Folks,

I am searching for client server program using socketAppender for log4cxx.
I will run it in Linux.
I found similar conversation in the apache archive but could not get the
source code of client server  program.

My ultimate goal is to run multiple client to write log and one single
server to consolidate it.
Client must be in c++,server can be written in anything.

Please help me in this. Thanks in advance.

Best Regards,
Soumik Sur.

[ANNOUNCEMENT] Apache Log4j 2.0-beta7 released

Ralph Goers — 2013-06-08T18:14:06

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta7 release!

Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to
Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides
many of the improvements available in Logback while fixing some inherent problems in Logback's
architecture.

This is the ninth release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

New features:
o LOG4J2-10: Break up core into multiple osgi jars. Thanks to Timothy Ward.
o LOG4J2-229: New JDBC, JPA, and NoSQL database Appenders. Thanks to beamerblvd.
o LOG4J2-251: Provide configuration information (location, content type, content if possible) via a registered Advertiser.

Fixed Bugs:
o LOG4J2-263: Do not allow a charset on RFC5424Layout - use UTF-8.
o LOG4J2-242: StringFormattedMessage and MessageFormatMessage now will accept a Throwable as their last argument and
pass it on.
o LOG4J2-269: Use transaction when batch size is 1.
o LOG4J2-268: Add guid to FlumeEvent headers for non-Map Messages.
o LOG4J2-246: Data buffer is reset in finally clause.
o LOG4J2-228: UDP now sends one event per packet.
o LOG4J2-261: Add missing "not" to error message. Thanks to Edward Sargisson.
o LOG4J2-223: Remove LoggerContext when LoggerContext is stopped.
o LOG4J2-260: XML layout does not specify charset in content type.
o LOG4J2-259: HTML layout does not specify charset in content type.
o LOG4J2-258: HTML layout does not output meta element for charset.
o LOG4J2-257: XML layout ignores charset for the XML processing intruction's encoding attribute.
o LOG4J2-255: Multi-byte character strings are now assumed to be in the platform default encoding, not UTF-8.
o LOG4J2-254: Mark OutputStream in OutputStreamManager as volatile. Mark header and footer as final.
o LOG4J2-244: Rewrite Appender was ignoring filters on referenced appenders.
o LOG4J2-245: Avoid EmptyStack exception if getCallerClass and SecurityManager are not available.
o LOG4J2-247: SocketServer.isActive should be volatile because it is accessed from different threads.

Changes:
o LOG4J2-249: Allow context parameters in Log4jContextListener to include properties.
o LOG4J2-243: Allow custom LogEventFactories.
o LOG4J2-262: Add support for interceptors in the embedded Flume Appender. Thanks to Edward Sargisson.
o Method name changes in interface org.apache.logging.log4j.spi.ThreadContextMap:
getContext() to getCopy(), get() to getImmutableMapOrNull().
o LOG4J2-154: Improve ThreadContext performance with copy-on-write map and stack.

Apache Log4j 2.0-beta7 requires a minimum of Java 6 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

[ANN] Dominik Psenner to join the Apache Logging PMC

Christian Grobmeier — 2013-06-03T08:38:21

Dear all,

it's my pleasure that Dominik Psenner, mostly active in log4net, has
been elected into the Apache Logging PMC. Congratulations!

All the best for your new role Dominik and thank you for your valuable
contributions so far.

Regards,
Christian

[ANNOUNCEMENT] Apache Log4j 2.0-beta6 released

Ralph Goers — 2013-05-12T06:09:52

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta6 release!

This is the eighth release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

Fixed Bugs:
o LOG4J2-231: Logger.getParent() was not returning the correct Logger.
o LOG4J2-201: Renamed Plugin annotation attribute from "type" to "category".
o LOG4J2-219: Fix: install default root logger if not configured (this is unchanged),
but make sure to include configured named loggers. Clarified documentation. Thanks to Peter DePasquale.
o LOG4J2-159: Use OSGi version format in Fragment-Host
o LOG4J2-234: RegexFilter threw a NullPointerException when used as a context-wide filter.
o LOG4J2-192: Add support for interpolating Environment variables when processing the configuration.
o LOG4J2-235: Removed dependency on tools jar from core module, made jconsole dependency optional. Thanks to Sebastian Oerding.
o LOG4J2-233: Fixed link to log4j-user mailing list.
o LOG4J2-222: Disruptor will now shutdown during Tomcat shutdown. Thanks to Steven Yang.
o LOG4J2-224: The FlumeAppender failed to start if the Flume RPCClient could not connect to any Flume agents.
o LOG4J2-223: Fix LoggerContext start and stop to eliminate IllegalStateException and NoClassDefFound errors.
o LOG4J2-221: Remove hundreds of compiler warnings. Thanks to Nick Williams.
o LOG4J2-215: Various small documentation fixes.
o LOG4J2-217: Ensure PluginManager streams are always closed. Thanks to Fabien Sanglard.

Changes:
o LOG4J2-237: Moved JMX Client GUI classes into separate jmx-gui submodule.
o LOG4J2-230: Improved error reporting when misconfigured. Thanks to Wojciech Zaręba.
o Renamed AsynchAppender to AsyncAppender. Plugin name became Async (was Asynch).
o Removed CheckStyle false positives for NewlineAtEndOfFile and whitespace following '*' at end of line in javadoc.
o Moved Clock interface to package org.apache.logging.log4j.core.helpers.
o LOG4J2-225: Documentation updates to clarify use and impact of location in pattern layouts.

Apache Log4j 2.0-beta6 requires a minimum of Java 6 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

log4cx: attic or incubation?

Christian Grobmeier — 2013-05-03T09:19:34

Hello folks,

please look at these few e-mails:
http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/201304.mbox/browser

For me there are two ways for log4cxx: incubation or attic.

I was outreaching for devs on log4cxx and got a few responses. It seems a couple
of people are interested in continuing this component. Most of them
said they might apply a couple of patches here and there, but nobody
burst out in emotions saying, YAY, this is it.

Without such a person I guess we have little chance in the incubator.
Maybe I am having a wrong view on it, so I ask you to voice your
opinion.

For now I would like to propose that I am cloning log4cxx to my GitHub
account and move the svn repos to the attic. That way I can overlook
if there is a team growing around log4cxx or not. Also I can ask for
ICLAs before accepting pull requests, which should help when we go
back to incubation. If there is, we can go back to incubation at any
time. If there is not, then well, no harm done.

Comments?

Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

[ANNOUNCEMENT] Apache Log4j 2.0-beta5 released

Ralph Goers — 2013-04-25T06:17:31

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-beta5 release!

This is the seventh release of Log4j 2 and is being made available to encourage use and feedback from the community.

Bug fixes and enhancements

Changes in this version include:

New features:
o LOG4J2-207: Add JMX support. Thanks to Remko Popma.
o LOG4J2-187: Add tag library. Thanks to Nick Williams.
o LOG4J2-164: Add methods is/setEndOfBatch to LogEvent. Thanks to Remko Popma.
o LOG4J2-163: Add support for asynchronous loggers. Thanks to Remko Popma.
o LOG4J2-179: Add Logger interface APIs to log at given levels.
o Added FlumePersistentManager which writes to BerkeleyDB and then writes to Flume asynchronously.
o LOG4J2-155: Expose file appender configuration details via an advertisement mechanism.

Fixed Bugs:
o LOG4J2-205: Fix deadlock in SocketAppender. Added option to not wait for socket reconnect.
o LOG4J2-211: Removing extra spaces in entry and exit method output. Thanks to Nick Williams.
o LOG4J2-212: Loggers without a "." had no parent logger.
o LOG4J2-212: Call LoggerContext.stop when the application is shutdown.
o LOG4J2-210: MapMessage was not enclosing key value in quotes when generating XML. Thanks to Arkin Yetis.
o LOG4J2-198: FlumeAvroManager now uses Flume RPCClient.
o LOG4J2-196: FlumeAvroManager now uses Flume RPCClient.
o LOG4J2-207: Use the Maven group ID org.apache.logging.log4j for all artifacts.
o LOG4J2-195: Unit tests now create files in the target directory. Thanks to Remko Popma.
o LOG4J2-193: RollingFastFileAppender (in log4j-async) did not roll over. Thanks to Remko Popma.
o LOG4J2-199: Highlight subprojects in sub-navigation. Thanks to Remko Popma.
o LOG4J2-200: LoggerContext method renamed to removeFilter from removeFiler. Thanks to Remko Popma.
o LOG4J2-194: ThrowableFormatOptionsTest failed on Windows due to CR/LF issue. Thanks to Remko Popma.
o LOG4J2-190: BaseConfiguration addLoggerAppender saved appender using the Logger name. Thanks to Werner.
o LOG4J2-189: The blocking parameter did not work properly on AsynchAppender. Thanks to Werner.
o LOG4J2-188: appender-refs on AsynchAppender didn't support the level and filter elements. Thanks to Werner.
o LOG4J2-176: Avoid IllegalArgumentException in AsynchAppender. Thanks to Remko Popma.
o LOG4J2-181: OutputStreamManager now adds the layout header whenever the OutputStream is set.
o LOG4J2-177: Fix NullPointerException in DatagramOutputStream when flush is called from multiple threads. Thanks to Remko Popma.
o LOG4J2-175: Plugin cache should be reset when addPackages is called.
o LOG4J2-159: Add Fragment-Host to MANIFEST.MF for log4j2-core. Thanks to Jan Winter.
o LOG4J2-167: Configurator throws a ClassCastException if LogManager returns a SimpleLoggerContext.
o LOG4J2-169: ConfigurationFactory was adding factories on every call.
o LOG4J2-161: Modify ClassLoaderContextSelector to use the first ClassLoader in the child parent hierarchy that
has a Context with a configuration to allow JSPs to use the WebApp's context and configuration.

Changes:
o LOG4J2-214: Async documentation update. Thanks to Remko Popma.
o LOG4J2-208: Move async subproject into core. Thanks to Remko Popma.
o LOG4J2-160: Move Throwable pattern converter options processing to ThrowableFormatOptions class. Thanks to Joanne Polsky.
o LOG4J2-157: Allowed Loggers access to the properties in the LoggerConfig. Thanks to Remko Popma.
o LOG4J2-153: Added ability to include or exclude location information. Thanks to Remko Popma.
o LOG4J2-151: Allow Logger and LoggerContext to be subclassed. Thanks to Remko Popma.

Apache Log4j 2.0-beta5 requires a minimum of Java 6 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j-1.2-api component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

Mirroring Log4J 2 on GitHub

Andrus Adamchik — 2013-03-18T12:09:32

Hey guys,

There's a Log4J mirror on GitHub at https://github.com/apache/log4j . Would it be possible to also mirror Log4J2? 

We've recently switched to Log4J2 on one of the big projects that I am doing. Now we need to patch a few things for our work in a way that is likely not going to be accepted back to Log4J. Specifically we want to short-circuit Log4jLogEvent.getSource to return a fixed String. We are using AsynchAppender and 'Log4jLogEvent.getSource' is a noticeable performance bottleneck for us, and we currently don't see a better way around it (ok, to be completely honest, we just don't have the cycles to refactor Log4J2 properly). So the idea was to keep a GitHub fork and merge periodically with the master copy.

Any thoughts/comments on exposing "2" on GitHub. 

As an Apache member I can probably ping infra myself. But wanted to talk to the 'logging' community first.

Thanks,
Andrus

Daily gump builds

Dominik Psenner — 2013-02-25T10:52:58

Hey,

Is there an easy way to get my hands on the daily builds gump does for us? Maybe there is a documentation somewhere that i haven't
found? Until now I crawled myself through here:

http://vmgump.apache.org/gump/public/index.html

without success.

Cheers,
Dominik

Moving log4cxx to the Attic

Christian Grobmeier — 2013-02-07T05:31:53

Hello

I would like to propose we move the log4cxx component to the attic.
I am not sure if the Apache Attic itself is the right place:
http://attic.apache.org/

as it seems to feed on TLDs only. I will ask there, if we agree that
log4cxx is not really maintained and that there will no work happen in
future.

I have hoped that there were a couple of people coming back to the
project when they see somebody is committing their patches. But it
hasn't happened and my own C skills are not enough to push this (time
is an issue too).

In case we agree, I would like to to keep the old log4cxx website,
saying this project is not longer maintained and the source code has
been moved to attic (if the attic.apache.org would take it). Other
options are also welcome, just let me hear what you think.

Best regards,
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

[ANNOUNCEMENT] Apache Log4j 2.0.beta4 released

Ralph Goers — 2013-02-01T16:15:26

The Apache Logging team is pleased to announce the Apache log4j 2.0-beta4 release!

This is the sixth release of Log4j 2 and is being made available to encourage use and feedback from the community\\

Changes in this version include:

New features:
o Added Log4j 2 to SLF4J adapter.
o LOG4J2-131: Add SMTPAppender. Thanks to Scott Severtson.
o Added hostName and contextName to property map.
o Add MessageFormatMessage and FormattedMessage.
o LOG4J2-134: Use %red, %white, %blue, and so on in the console appender.
o LOG4J2-133: Allow custom message creation via a message factory.
o Added Flume Appender samples.

Fixed Bugs:
o LOG4J2-156: LocalizedMessageTest fails on linux system. Thanks to Andreas Born.
o LOG4J2-152: RollingFileAppender's FileRenameAction was throwing a NullPointerException if no directory was specified
on the target file name. Thanks to Remko Popma.
o LOG4J2-150: Convert all System.getProperty calls to use PropertiesUtil to suppress SecurityExceptions.
o LOG4J2-147: ThreadContextMapFilter was matching on the key instead of the value of the key. Thanks to William Burns.
o Allow FlumeAvroManager to initialize even if it cannot connect to an agent.
o LOG4J2-149: SMTPAppender will only cache filtered events. Thanks to Scott Severtson.
o LOG4J2-145: Add missing serial version IDs.
o LOG4J2-144: NullPointerException in RFC5424Layout.
o LOG4J2-143: MessagePatternConverter now returns "null" if the log message is null.
o LOG4J2-142: Serialized LogEvents were not reset in the output stream causing them to deserialize incorrectly.
o LOG4J2-139: Fix null pointer exception in SocketAppender if no protocol is specified. The protocol will default
to TCP for the SocketAppender and UDP for the SyslogAppender.
o LOG4J2-140: Typo in documentation of SocketAppender. Thanks to Joern Huxhorn.
o LOG4J2-137: Fix hang in Dumbster SMTP test server.
o LOG4J2-130: PatternLayout should format throwables without requiring a converter.
o LOG4J2-135: BaseConfiguration does not close the first appender. Thanks to Ingo Feltes.
o LOG4J2-132: AbstractLogger.catching(Throwable) checks for DEBUG level but logs at ERROR level.
o LOG4J2-129: RoutingAppender was only creating a single appender for the default Route.
o LOG4J2-126: Allow JMS appenders to recover if the queue or topic is unavailable.
o LOG4J2-127: AbstractLogger methods were not passing Markers to the isEnabled methods.
o LOG4J2-125: JMSQueue and JMSTopic Appenders did not allow name to be specified.
o LOG4J2-111: Enhanced javadoc copyright statement.
o LOG4J2-120: TCPSocketManager would fail if the initial connection could not be established.
o LOG4J2-119: A broken socket connection would cause the TCPSocketManager to continuously reconnect.
o LOG4J2-123: The example for ThreadContextMapFilter was incorrect. Thanks to Olivier Lamy.
o LOG4J2-116: File renaming was using the wrong date value. Enhanced DefaultRolloverStrategy to store newest files in
highest index as well as lowest.
o LOG4J2-115: ThreadContext Map elements with null values are now ignored when constructing a Flume event and in the
RFC5424 Layout.
o LOG4J2-113: StructuredDataFilter createFilter was annotated with PluginAttr instead of PluginElement for the
KeyValuePairs.
o LOG4J2-114: StructuredDataMessage was validating the length of the values in the event Map instead of the lengths
of the keys. Thanks to Arkin Yetis.

Changes:
o LOG4J2-136: Allow newlines to be escaped in Syslog and RFC5424 layouts. Allow Throwables to be included in
the output from RFC5424Layout. Thanks to Scott Severtson.
o LOG4J2-128: Add follow attribute to Console Appender.
o LOG4J2-122: Add unit test to verify exceptions are thrown when the socket connection fails.
o LOG4J2-110: Renamed log4j12-api to log4j-1.2-api.

Apache Log4j 2.0-beta4 requires a minimum of Java 5 to build and run. Basic compatibility with
Log4j 1.x is provided through the log4j12-api component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

Distribution directories

Ralph Goers — 2013-01-31T18:00:16

As part of the release of Log4j 2.0-beta4 I copied all the current release artifacts from http://www.apache.org/dist/logging/to https://dist.apache.org/repos/dist/release/logging/.  Any future releases should be published through this location in subversion instead of the prior location via people.apache.org.

Ralph

How to log to the Data Base

Timur Nurlygayanov — 2013-01-07T14:40:09

Hi all,

I new user of log4j and I want to store my logs into the Data Base (like
MySQL), but looks like I can't do this with new beta version of the library
log4j2.

Probably you can send link or instruction how I can do this.


Regards,
Timur Nurlygayanov

Please update your fingerprints on id

Christian Grobmeier — 2013-01-02T10:25:17

Hello folks,

if you are not listed here:
http://people.apache.org/keys/group/logging-pmc.asc

its time to go to id.apache.org and add your fingerprint. You'll then
appear in the file after a while.

Today I was looking at an issue with my key not here:
http://www.apache.org/dist/logging/KEYS

The file has much more names than in the link above, but not all
necessary. I believe we should use the option by id.apache.org for
log4j2. For now I will add my key to the old file too, so the issue
should be fixed

Cheers
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Log4php git repository is live

Ivan Habunek — 2012-12-08T11:26:07

Hi all,

Thanks to Gavin from Infra, our git repository is live as of today.
This marks the end of svn for log4php code. The svn repo will remain
available in read-only mode.

Here's the links you might need:

The official repository (and web interface), writable for developers:
https://git-wip-us.apache.org/repos/asf/logging-log4php.git

Official read-only mirror:
git://git.apache.org/logging-log4php.git

Github read-only mirror:
https://github.com/apache/logging-log4php

Note that the old apache and github mirrors, which were named
"log4php.git" instead of the current name "logging-log4php.git" will
be removed at some point in time, so don't use those for anything.

The github mirror is updated once daily. I was told that it's not
possible to update on commit since it's a mirror of the git.apache.org
mirror, and not of the main repository. I will look into possible ways
of improving this.

None of the other Logging Services projects are affected by this
change, except in a way to encourage them to move to git at some point
in time. The transition was very painless.

Best regards,
Ivan

On using G+ / Twitter

Christian Grobmeier — 2012-12-03T14:52:01

Hi,

I would like to propose that we utilize G+ and Twitter more. We have
done so with G+
https://plus.google.com/b/104876804201453912446/104876804201453912446/posts

and I think it would be cool to have f.e. < at >asflogging
were we can point people to the right resources, answer simple
questions or spread our news.

One thing we could spread is articles like that:
http://www.dzone.com/links/r/using_log4net_in_web_applications.html

I am willing to step up on this. G+ is already shared between Ivan and
myself. If anybody else is interested, please let us know.

If there are any objections, let us know also :-)

Cheers
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Apache Logging Services IRC channel

Ivan Habunek — 2012-11-28T19:40:57

I just registered #asflogging channel on irc.freenode.net. Everyone's
welcome for any logging related discussions, including all
subprojects, or just for hanging out.

Please come join me so I won't be all alone. :)

Regards,
Ivan

FW: Add new FAQ entry

Dominik Psenner — 2012-11-28T07:20:48

Hi,

Yesterday I posted this message on log4net-dev but maybe noone noticed. :-)
Is there someone around that knows how the publishing of the log4net website
works?

Cheers,
D.

Moving to svnpubsub for dist artifacts

Ralph Goers — 2012-11-27T20:32:13

While we migrated the web site to the CMS we never handled the second part.  We need to stop publishing artifacts to p.a.o by the end of the year and commit them to https://dist.apache.org/repos/dist/release/logging instead.

Ralph

How to contribute and revive log4cxx

Christian Grobmeier — 2012-11-27T19:52:45

Hello all,

today I submitted a patch by Andrew Lazarus to log4cxx. My feeling is
that there is still some interest in log4cxx and I would like to help
the contributors to submit their patches. I am waiting for JIRA access
to close the issues I fixed.

I would like to invite everybody to help reactivating log4cxx!

As some of you might know I am not a skilled C programmer, thats why I
cannot can stay here permanently. Instead my plan is to help
interested persons to learn about the Apache way and to bring in their
changes - not only as contributor but also a committer later.

If this strategy does not work out I am afraid that log4cxx will
become food for the always hungry attic. The attic is the place where
unmaintained Apache projects reside.

If you are reading this and would like to help log4cxx any further,
please read this first:

* http://www.apache.org/foundation/how-it-works.html

It will explain *what* the ASF actually is.
If you like what you read and if you are seriously interested in
contributing patches and maybe becoming a committer yourself, please
sign and fax/mail the ICLA:

http://www.apache.org/licenses/icla.txt

We can only accept bigger contributions when we have this on file. If
any questions ping me, I will try to respond with all my knowledge
about it or refer you to the right place.

As a workflow, we should use the following:

- please open a JIRA issue for your change
- attach a SVN diff file to it
- come to the mailinglist, explain what you have changed and hopefully
get some feedback from other contributors

Please feel free to ping the log4cxx-dev list for any more questions.
It is also a good thing to subscribe to:

general-subscribe< at >logging.apache.org

The general list is the place where we discuss general issues, like
for example the health of a sub project like log4cxx.

My hope is that with applying the great patches of Andrew will
motivate others around might find their way to this project again.

All the best,
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Logging groups normalization

Christian Grobmeier — 2012-11-18T19:46:11

Hi all,

just normalized the groups as we discussed previously. The
logging-log4* groups were already obsolete as LDAP is king (so i
understood it). Therefore it was no problem for me to remove these
groups.

Now we have the usual logging and logging-pmc group. Both have full
access to /logging

if somebody of you has problems with SVN access please let me know.

Thanks!
Christian

--
http://www.grobmeier.de
https://www.timeandbill.de

Commit rights in Logging

Christian Grobmeier — 2012-11-15T18:46:29

Hi all,

I have several groups here:
http://people.apache.org/committers-by-project.html#logging

Like:
log4cxx
log4j
log4j2
log4php

and so on. Ivan wants to commit to log4j (the site) but he doesn't
have the group. So he ask me if he has enough rights. I myself have no
log4j group, but I can commit to log4j. Not sure why or if this is by
design.

I think these sub groups are pretty useless and would like to propose
that we just have two groups: logging and logging-pmc.

Personally I think there is no need for separation; if Ivan wants to
contribute to log4j and has been elected as logging committer, he
should be able to do that.

What do you think?

Cheers
Christian