svn commit: r1556140 - /incubator/log4cxx/trunk/pom.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 08:19:12 2014
New Revision: 1556140

URL: http://svn.apache.org/r1556140
Log:
aplhabetical order of committers

Modified:
incubator/log4cxx/trunk/pom.xml

Modified: incubator/log4cxx/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/pom.xml?rev=1556140&r1=1556139&r2=1556140&view=diff
==
--- incubator/log4cxx/trunk/pom.xml (original)
+++ incubator/log4cxx/trunk/pom.xml Tue Jan  7 08:19:12 2014
@@ -65,6 +65,15 @@



+   alexz
+   Alex Zbarcea
+   al...@apache.org
+   America/New York
+   
+   Committer
+   
+   
+   
chand
Chand Priyankara
ch...@apache.org
@@ -73,6 +82,15 @@
Committer


+
+fseydoux
+Florian Seydoux
+fseyd...@apache.org
+Europe/Zurich
+
+Committer
+
+

joseph
Joseph Southwell
@@ -92,15 +110,6 @@



-   alexz
-   Alex Zbarcea
-   al...@apache.org
-   America/New York
-   
-   Committer
-   
-   
-   
tschoening
Thorsten Schöning
tschoen...@apache.org
@@ -109,15 +118,6 @@
Committer

 
-
-fseydoux
-Florian Seydoux
-fseyd...@apache.org
-Europe/Zurich
-
-Committer
-
-


afester

svn commit: r1556143 - /incubator/log4cxx/trunk/src/changes/changes.xslt

[tschoening]

Author: tschoening
Date: Tue Jan  7 08:33:54 2014
New Revision: 1556143

URL: http://svn.apache.org/r1556143
Log:
The xslt doesn't seem to be used anymore and had old content until 0.10.0, but 
the web site already showed 0.11.0.

Removed:
incubator/log4cxx/trunk/src/changes/changes.xslt

svn commit: r1556144 - /incubator/log4cxx/trunk/src/changes/changes.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 08:38:24 2014
New Revision: 1556144

URL: http://svn.apache.org/r1556144
Log:
Fixed indentation

Modified:
incubator/log4cxx/trunk/src/changes/changes.xml

Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/changes/changes.xml?rev=1556144&r1=1556143&r2=1556144&view=diff
==
--- incubator/log4cxx/trunk/src/changes/changes.xml (original)
+++ incubator/log4cxx/trunk/src/changes/changes.xml Tue Jan  7 08:38:24 2014
@@ -16,417 +16,365 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 
-  -->
+-->
 
-
-Apache log4cxx
-
-
-
-Errors when compile log4cxx 0.10.0 under Win7 x64 
with Visual Studio 2010 (due to Christian Boos and Feng Nan)
-possibly wrong use of autotools docdir (due to Alex 
Zbarcea)
-log4cxx doesn't compile on openembedded (due to 
Alex Zbarcea)
-Console appender crashes if layout is not 
set
-socketappendertestcase and 
xmlsocketappendertestcase not run
-Bad link to log4cxx-dev archive
-Eliminate anachronism warnings
-Eliminate Extra ";" ignored warnings
-Local variables hide member variables
-Add ability to compile out logging by logging 
level.
-MDC::put will not overwrite existing key value 
pair
-Apache log4cxx 0.11.0 release
-Headers cannot be included with very strict warning 
settings
-AndFilter and others defined but not 
implemented
-Reconnection not working for sockets
-Threads for reconnecting sockets do not end cleanly 
when program exits
-tests and sample code unnecessarily compiled during 
default make target
-Sun Studio 11 reports function hides base virtual 
function warning
-Thread::sleep not affected by 
Thread::interrupt.
-Suspicious, but harmless, reuse of LOCAL1 in 
SyslogAppender
-Unit tests fail to compile with xlc_r on 
AIX
-LevelRangeFilter has default value for 
acceptOnMatch that is different from log4j
-gcc 4.3 requires #include  when 
using memcpy and related. 
-Unnecessary trailing semi-colons after LOG4CXX_INFO 
et al in docs, examples and tests.
-Tab characters are not recognized in property 
files.
-Value continuation does not properly handle CRLF in 
property files.
-Escape sequences not recognized in property 
files.
-SMTPAppender does not build properly with 
autotools.
-odbcappender.cpp does not compile with unixODBC on 
linux.
-ODBCAppender connection settings broken (or just 
have changed).
-DOMConfigurator does not set ErrorHandler.
-BasicConfigurator::configure results in writer not 
set warning.
-Transcoder::encodeCharsetName bungles 
encoding
-Download page does not have link to KEYS 
file
-Unit tests fail on system dates later than 
2009-12-31.
-Log4cxx triggers locking inversion which can result 
in a deadlock.
-
-
-logger.h includes config.h
-Missing #else
-initialization not working on many OS's
-Preprocessor macro WIN32 used instead of 
_WIN32
-Win32 OutputDebugString
-SocketAppender binary format not compatible with 
Chainsaw
-Compilation problems using VC5 or VC6 with later 
Platform SDKs
-Conflicting definitions of tchar.h/simulatenous 
Unicode+MBCS
-Timezone may have side-effects
-the threshold  of ApenderSkeleton can not be set by 
calling setOption.
-Add branch optimization hint to LOG4CXX_DEBUG 
macro
-add -Wall to compile log4cxx will get many 
warning
-PatternLayout don't use locale time zone,it's use 
GMT tome zone
-Misleading statements in Introduction to 
log4cxx
-Use of non reentrant time functions
-LoggerStream Feature
-Add .cvsignore's to ignore generated files
-Add check that libxml2 not libxml has been 
included
-Backslashes in filenames in XML config of 
FileAppender broken
-Unit tests have become stale
-Class and module name not available in 
LogEvent
-Add Ant+cpptasks build file
-Default initialization is broken
-Appender threshold cannot be set in configuration 
files
-Appender threshold cannot be set in configuration 
files
-Appender attributes are not passed passed to 
setOption correctly.
-StringTokenizer uses evil strtok and wcstok 
functions
-Missing const qualifiers, Exception::getMessage() in 
particular.
-Missing copy constructors and assignment 
operators
-log4cxx::Exception is not derived from 
std::exception
-Visual Studio 6 CVS build broken
-Avoid use of MSXML
-Migrate to Apache Portable Runtime threads
-Unable to build log4cxx under Borland C++
-Remove DailyRollingFileAppender
-PatternLayout does not support Java date format 
specifiers
-Layout timestamp doesn't seem to adjust for daylight 
saving
-configure/make help needed
-GUMP integation
-_T causes error : 1048576 cannot be used as a 
function
-Extra semicolon after namespace closing 
paren
-Check headers for missing declarations and Effective 
C++ violations
-Use hex representation for thread identifier
-Move timezone specification into pattern, remove 
locale specification
-variable name clash in macro
-Migrate log4

Re: Incubation requirements

[Christian Grobmeier]

On 6 Jan 2014, at 23:13, Thorsten Schöning wrote:


Guten Tag Christian Grobmeier,
am Montag, 6. Januar 2014 um 20:10 schrieben Sie:


In example we need to add an "incubation logo" to the site like here:
http://incubator.apache.org/wave/


Should this be added additionally or replace the current Apache
logging logo? As I'm looking on the build process of the site
currently anyways, I could implement the logo.


I would add it to the right side. I think there is even a maven tag for 
it,

like  or so



http://www.apache.org/foundation/marks/pmcs#introduction


From my understanding we are missing the disclaimer and naming, too.

Should the disclaimer simply be added on the main index page? It's
pretty long and the disclaimer may not get recognized. We could split
up the main index page to only contain introduction and disclaimer and
get the other content into another file with it's own menu item,
something like "How to use".


Basically its up to you. I agree fully with you the main page is too 
long

and it looks a bit 80ties.

While we are at it, you might want to enable the Maven Fluido Skin which
provides a great look and feel:

https://maven.apache.org/skins/maven-fluido-skin/

Apache "Podling-Name" is currently undergoing Incubation at the 
Apache Software Foundation.


This sentence could be added as the first sentence of the introduction
as well.


+1

Thanks a lot!

Christian



Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow



---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB

Re: Incubation requirements

[Thorsten Schöning]

Guten Tag Christian Grobmeier,
am Dienstag, 7. Januar 2014 um 09:40 schrieben Sie:

> https://maven.apache.org/skins/maven-fluido-skin/

Hello,

I already had a look at the different skins and how templates are
generated, but I don't seem to understand how those should work. The
default skin is missing maven-base.css in the distribution and the
fluido skin adds a minified css file, but it doesn't contain any of
the classes used in XHTML and itself is not mentioned in the generated
XHTML at all.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

svn commit: r1556208 - in /incubator/log4cxx/trunk: DISCLAIMER pom.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 13:09:55 2014
New Revision: 1556208

URL: http://svn.apache.org/r1556208
Log:
incubation info added

Added:
incubator/log4cxx/trunk/DISCLAIMER
Modified:
incubator/log4cxx/trunk/pom.xml

Added: incubator/log4cxx/trunk/DISCLAIMER
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/DISCLAIMER?rev=1556208&view=auto
==
--- incubator/log4cxx/trunk/DISCLAIMER (added)
+++ incubator/log4cxx/trunk/DISCLAIMER Tue Jan  7 13:09:55 2014
@@ -0,0 +1 @@
+Apache Podling-Name is an effort undergoing incubation at The Apache Software 
Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is 
required of all newly accepted projects until a further review indicates that 
the infrastructure, communications, and decision making process have stabilized 
in a manner consistent with other successful ASF projects. While incubation 
status is not necessarily a reflection of the completeness or stability of the 
code, it does indicate that the project has yet to be fully endorsed by the ASF.
\ No newline at end of file

Modified: incubator/log4cxx/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/pom.xml?rev=1556208&r1=1556207&r2=1556208&view=diff
==
--- incubator/log4cxx/trunk/pom.xml (original)
+++ incubator/log4cxx/trunk/pom.xml Tue Jan  7 13:09:55 2014
@@ -6,9 +6,9 @@
apache-log4cxx
pom
0.11.0-SNAPSHOT
-   Apache log4cxx
+   Apache log4cxx (Incubating)
Logging framework for C++.
-   http://logging.apache.org:80/log4cxx
+   http://incubator.apache.org/log4cxx

JIRA
https://issues.apache.org/jira/browse/LOGCXX

svn commit: r1556210 - /incubator/log4cxx/trunk/src/changes/changes.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 13:30:12 2014
New Revision: 1556210

URL: http://svn.apache.org/r1556210
Log:
Renamed title to better reflect the current page.

Modified:
incubator/log4cxx/trunk/src/changes/changes.xml

Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/changes/changes.xml?rev=1556210&r1=1556209&r2=1556210&view=diff
==
--- incubator/log4cxx/trunk/src/changes/changes.xml (original)
+++ incubator/log4cxx/trunk/src/changes/changes.xml Tue Jan  7 13:30:12 2014
@@ -19,7 +19,7 @@
 -->
 

-   Apache log4cxx
+   Changes

 

svn commit: r1556229 [1/2] - /incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in

[tschoening]

Author: tschoening
Date: Tue Jan  7 14:48:09 2014
New Revision: 1556229

URL: http://svn.apache.org/r1556229
Log:
Updated doxyfile to 1.8.6 to properly build the apidocs

Modified:
incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in

doxygen.css and GPL

[Thorsten Schöning]

Hello,

I'm now able to generate apidocs using doxygen and the maven build
scripts and recognized, that there's some code to replace the
doxygen.css and tabs.css with almost unusable style definitions. The
comment says something about GPL, but the original files don't seem
to have any GPL statement (anymore?) and on the Doxygen homepage
itself one can find the following sentence:

> Documents produced by doxygen are derivative works derived from the
> input used in their production; they are not affected by this
> license.

To me this reads like we can simply remove the changes to the
stylesheets and use the original ones, am I correct? Else I ask myself
why we don't need to change the JavaScript files and maybe images,
too. The docs look really ugly without those stylesheets.

Following is the code used to replace the file contents:



/*
&license;
*/
/*  Minimal replacement for GPL'd doxygen.css  */


/*
&license;
*/
/*  Minimal replacement for GPL'd tabs.css  */
DIV.tabs {
display : none ;
}


Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

svn commit: r1556242 - /incubator/log4cxx/trunk/build.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 15:25:49 2014
New Revision: 1556242

URL: http://svn.apache.org/r1556242
Log:
We want to be able to produce new apidocs without all the other dependencies 
and compiling the software. Additionally I removed some changes to Doxygen's 
default CSS files, because I think those are not needed anymore, and to 
maven-theme.css because the bug got resolved upstream.

Modified:
incubator/log4cxx/trunk/build.xml

Modified: incubator/log4cxx/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/build.xml?rev=1556242&r1=1556241&r2=1556242&view=diff
==
--- incubator/log4cxx/trunk/build.xml (original)
+++ incubator/log4cxx/trunk/build.xml Tue Jan  7 15:25:49 2014
@@ -1791,7 +1791,6 @@

 


-
-   
-   
-   /*
-   &license;
-   */
-   /*  Minimal replacement for GPL'd doxygen.css  */
-   
-   
-   /*
-   &license;
-   */
-   /*  Minimal replacement for GPL'd tabs.css  */
-   DIV.tabs {
-   display : none ;
-   }
-   
-
-

 

svn commit: r1556243 - /incubator/log4cxx/trunk/pom.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 15:26:46 2014
New Revision: 1556243

URL: http://svn.apache.org/r1556243
Log:
Fixed some errors for commented maven goals so we are able to build the site 
including apidocs now.

Modified:
incubator/log4cxx/trunk/pom.xml

Modified: incubator/log4cxx/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/pom.xml?rev=1556243&r1=1556242&r2=1556243&view=diff
==
--- incubator/log4cxx/trunk/pom.xml (original)
+++ incubator/log4cxx/trunk/pom.xml Tue Jan  7 15:26:46 2014
@@ -158,17 +158,17 @@
 


-   

maven-assembly-plugin

project site and apidocs build again

[Thorsten Schöning]

Hello,

I managed to get the project site and it's apidocs to build again
using maven and already made some changes to represent the incubation
status of the project. I needed to update dependencies of ant packages
and such stuff, therefore it may break on other systems than mine.
Additionally I changed dependencies in the ant build script so that
the creation of apidocs doesn't necessarily rely on the scanning for
apr and such stuff, else we wouldn't be able to create apidocs without
fullfilling dependencies of the build only useful for actually
compiling the software.

The targets and their dependencies and the mapping to maven goals
needs to be reworked in future, currently I found it useful to define
the goal "site" to only create the project site and the apidocs.

Could some of you please test the build? Something like "mvn clean
site" should be enough. If it works for others we could create the new
latest_stable-tag representing the current status of the project.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

svn commit: r1556255 - in /incubator/log4cxx/trunk/src/main/include/log4cxx: filter/denyallfilter.h filter/loggermatchfilter.h net/xmlsocketappender.h pattern/patternconverter.h

[tschoening]

Author: tschoening
Date: Tue Jan  7 16:02:12 2014
New Revision: 1556255

URL: http://svn.apache.org/r1556255
Log:
Corrected some Doxygen warnings.

Modified:
incubator/log4cxx/trunk/src/main/include/log4cxx/filter/denyallfilter.h
incubator/log4cxx/trunk/src/main/include/log4cxx/filter/loggermatchfilter.h
incubator/log4cxx/trunk/src/main/include/log4cxx/net/xmlsocketappender.h
incubator/log4cxx/trunk/src/main/include/log4cxx/pattern/patternconverter.h

Modified: 
incubator/log4cxx/trunk/src/main/include/log4cxx/filter/denyallfilter.h
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/filter/denyallfilter.h?rev=1556255&r1=1556254&r2=1556255&view=diff
==
--- incubator/log4cxx/trunk/src/main/include/log4cxx/filter/denyallfilter.h 
(original)
+++ incubator/log4cxx/trunk/src/main/include/log4cxx/filter/denyallfilter.h Tue 
Jan  7 16:02:12 2014
@@ -53,11 +53,11 @@ namespace log4cxx
 
 /**
 Always returns the integer constant {@link 
spi::Filter#DENY DENY}
-regardless of the {@link spi::LoggingEvent 
LoggingEvent} parameter.
+regardless of the {@link spi::LoggingEventPtr 
LoggingEvent} parameter.
 @param event The LoggingEvent to filter.
 @return Always returns {@link spi::Filter#DENY DENY}.
 */
-FilterDecision decide(const spi::LoggingEventPtr& /* 
event */) const
+FilterDecision decide(const spi::LoggingEventPtr& 
event) const
 { return spi::Filter::DENY; }
 }; // class DenyAllFilter
 

Modified: 
incubator/log4cxx/trunk/src/main/include/log4cxx/filter/loggermatchfilter.h
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/filter/loggermatchfilter.h?rev=1556255&r1=1556254&r2=1556255&view=diff
==
--- incubator/log4cxx/trunk/src/main/include/log4cxx/filter/loggermatchfilter.h 
(original)
+++ incubator/log4cxx/trunk/src/main/include/log4cxx/filter/loggermatchfilter.h 
Tue Jan  7 16:02:12 2014
@@ -42,8 +42,8 @@ namespace log4cxx
 spi::LoggingEvent LoggingEvent}, then the #decide method 
returns  {@link
 spi::Filter#ACCEPT ACCEPT} in case the AcceptOnMatch 
option value is set
to true, if it is false then {@link
-   spi::filter::Filter#DENY} is returned. If there is no match, {@link
-   spi::filter::Filter#NEUTRAL} is returned.  A loggerToMatch of "root"
+   spi::Filter#DENY} is returned. If there is no match, {@link
+   spi::Filter#NEUTRAL} is returned.  A loggerToMatch of "root"
matches both the root logger and a logger named "root".
 
*/

Modified: 
incubator/log4cxx/trunk/src/main/include/log4cxx/net/xmlsocketappender.h
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/net/xmlsocketappender.h?rev=1556255&r1=1556254&r2=1556255&view=diff
==
--- incubator/log4cxx/trunk/src/main/include/log4cxx/net/xmlsocketappender.h 
(original)
+++ incubator/log4cxx/trunk/src/main/include/log4cxx/net/xmlsocketappender.h 
Tue Jan  7 16:02:12 2014
@@ -42,7 +42,7 @@ namespace log4cxx
 XML stream representing a {@link spi::LoggingEvent LoggingEvent} object
 to the server side.
 
-   - Remote logging uses the TCP protocol. Consequently, if
+- Remote logging uses the TCP protocol. Consequently, if
 the server is reachable, then log events will eventually arrive
 at the server.
 
@@ -125,11 +125,11 @@ namespace log4cxx
 
   protected:
 virtual void setSocket(log4cxx::helpers::SocketPtr& socket, 
log4cxx::helpers::Pool& p);
-
+
 virtual void cleanUp(log4cxx::helpers::Pool& p);
-
+
 virtual int getDefaultDelay() const;
-
+
 virtual int getDefaultPort() const;
 
 void append(const spi::LoggingEventPtr& event, 
log4cxx::helpers::Pool& pool);
@@ -140,9 +140,9 @@ namespace log4cxx
 XMLSocketAppender(const XMLSocketAppender&);
 XMLSocketAppender& operator=(const XMLSocketAppender&);
 }; // class XMLSocketAppender
-
+
 LOG4CXX_PTR_DEF(XMLSocketAppender);
-
+
 } // namespace net
 } // namespace log4cxx
 

Modified: 
incubator/log4cxx/trunk/src/main/include/log4cxx/pattern/patternconverter.h
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/include/log4cxx/pattern/patternconverter.h?rev=1556255&r1=1556254&r2=1556255&view=diff
==
--- incubator/log4cxx/trunk/src/main/inclu

svn commit: r1556263 - in /incubator/log4cxx/trunk: pom.xml src/site/doxy/Doxyfile.in src/site/doxy/mainpage.dox

[tschoening]

Author: tschoening
Date: Tue Jan  7 16:18:46 2014
New Revision: 1556263

URL: http://svn.apache.org/r1556263
Log:
Optimized configuration of dixygen a bit, removed timestamps, activated 
generation of UML, removed unused file etc.

Removed:
incubator/log4cxx/trunk/src/site/doxy/mainpage.dox
Modified:
incubator/log4cxx/trunk/pom.xml
incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in

Modified: incubator/log4cxx/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/pom.xml?rev=1556263&r1=1556262&r2=1556263&view=diff
==
--- incubator/log4cxx/trunk/pom.xml (original)
+++ incubator/log4cxx/trunk/pom.xml Tue Jan  7 16:18:46 2014
@@ -224,13 +224,6 @@

replace="/trunk"

flags="g"
/>
-   
-   

-   




Modified: incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in?rev=1556263&r1=1556262&r2=1556263&view=diff
==
--- incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in (original)
+++ incubator/log4cxx/trunk/src/site/doxy/Doxyfile.in Tue Jan  7 16:18:46 2014
@@ -59,14 +59,14 @@ PROJECT_NUMBER = "Version @VERSI
 # for a project that appears at the top of each page and should give viewer a
 # quick idea about the purpose of the project. Keep the description short.
 
-PROJECT_BRIEF  =
+PROJECT_BRIEF  = 
 
 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
 # the documentation. The maximum height of the logo should not exceed 55 pixels
 # and the maximum width should not exceed 200 pixels. Doxygen will copy the 
logo
 # to the output directory.
 
-PROJECT_LOGO   =
+PROJECT_LOGO   = 
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
 # into which the generated documentation will be written. If a relative path is
@@ -125,7 +125,7 @@ REPEAT_BRIEF   = YES
 # the entity):The $name class, The $name widget, The $name file, is, provides,
 # specifies, contains, represents, a, an and the.
 
-ABBREVIATE_BRIEF   =
+ABBREVIATE_BRIEF   = 
 
 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
 # doxygen will generate a detailed section even if there is only a brief
@@ -159,7 +159,7 @@ FULL_PATH_NAMES= NO
 # will be relative from the directory where doxygen is started.
 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
 
-STRIP_FROM_PATH=
+STRIP_FROM_PATH= 
 
 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
 # path mentioned in the documentation of a class, which tells the reader which
@@ -168,7 +168,7 @@ STRIP_FROM_PATH=
 # specify the list of include paths that are normally passed to the compiler
 # using the -I flag.
 
-STRIP_FROM_INC_PATH=
+STRIP_FROM_INC_PATH= 
 
 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
 # less readable) file names. This can be useful is your file systems doesn't
@@ -223,7 +223,7 @@ SEPARATE_MEMBER_PAGES  = NO
 # uses this value to replace tabs by spaces in code fragments.
 # Minimum value: 1, maximum value: 16, default value: 4.
 
-TAB_SIZE   = 8
+TAB_SIZE   = 4
 
 # This tag can be used to specify a number of aliases that act as commands in
 # the documentation. An alias has the form:
@@ -235,13 +235,13 @@ TAB_SIZE   = 8
 # "Side Effects:". You can put \n's in the value part of an alias to insert
 # newlines.
 
-ALIASES=
+ALIASES= 
 
 # This tag can be used to specify a number of word-keyword mappings (TCL only).
 # A mapping has the form "name=value". For example adding "class=itcl::class"
 # will allow you to use the command class in the itcl::class meaning.
 
-TCL_SUBST  =
+TCL_SUBST  = 
 
 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
sources
 # only. Doxygen will then generate output that is more tailored for C. For
@@ -285,7 +285,7 @@ OPTIMIZE_OUTPUT_VHDL   = NO
 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
 # the files are not read by doxygen.
 
-EXTENSION_MAPPING  =
+EXTENSION_MAPPING  = 
 
 # If the MARKDOWN_SUPPORT tag is enabled then doxygen 

Re: Create new branches and revert trunk

[Florian Seydoux]

On 06.01.2014 18:25, Joseph Southwell wrote:
> Sounds good to me.
[...]
> On Jan 6, 2014, at 10:25 AM, Thorsten Schöning  wrote:
> [...]
>> Said that, "tags/latest_stable" would be much better than
>> "current_stable" and I would use this unless people shout at me.

+1

--
flo

svn commit: r1556291 - /incubator/log4cxx/trunk/src/changes/changes.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 17:54:38 2014
New Revision: 1556291

URL: http://svn.apache.org/r1556291
Log:
guessed issue types from messages

Modified:
incubator/log4cxx/trunk/src/changes/changes.xml

Modified: incubator/log4cxx/trunk/src/changes/changes.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/changes/changes.xml?rev=1556291&r1=1556290&r2=1556291&view=diff
==
--- incubator/log4cxx/trunk/src/changes/changes.xml (original)
+++ incubator/log4cxx/trunk/src/changes/changes.xml Tue Jan  7 17:54:38 2014
@@ -24,248 +24,248 @@
 


-   Errors when compile log4cxx 
0.10.0 under Win7 x64 with Visual Studio 2010 (due to Christian Boos and Feng 
Nan)
-   possibly wrong use of 
autotools docdir (due to Alex Zbarcea)
-   log4cxx doesn't compile on 
openembedded (due to Alex Zbarcea)
-   Console appender crashes if 
layout is not set
-   socketappendertestcase and 
xmlsocketappendertestcase not run
-   Bad link to log4cxx-dev 
archive
-   Eliminate anachronism 
warnings
-   Eliminate Extra ";" ignored 
warnings
-   Local variables hide member 
variables
-   Add ability to compile out 
logging by logging level.
-   MDC::put will not overwrite 
existing key value pair
-   Apache log4cxx 0.11.0 
release
-   Headers cannot be included 
with very strict warning settings
-   AndFilter and others defined 
but not implemented
-   Reconnection not working for 
sockets
-   Threads for reconnecting 
sockets do not end cleanly when program exits
-   tests and sample code 
unnecessarily compiled during default make target
-   Sun Studio 11 reports 
function hides base virtual function warning
-   Thread::sleep not affected 
by Thread::interrupt.
-   Suspicious, but harmless, 
reuse of LOCAL1 in SyslogAppender
-   Unit tests fail to compile 
with xlc_r on AIX
-   LevelRangeFilter has default 
value for acceptOnMatch that is different from log4j
-   gcc 4.3 requires #include 
 when using memcpy and related.
-   Unnecessary trailing 
semi-colons after LOG4CXX_INFO et al in docs, examples and tests.
-   Tab characters are not 
recognized in property files.
-   Value continuation does not 
properly handle CRLF in property files.
-   Escape sequences not 
recognized in property files.
-   SMTPAppender does not build 
properly with autotools.
-   odbcappender.cpp does not 
compile with unixODBC on linux.
-   ODBCAppender connection 
settings broken (or just have changed).
-   DOMConfigurator does not set 
ErrorHandler.
-   BasicConfigurator::configure 
results in writer not set warning.
-   Transcoder::encodeCharsetName bungles encoding
-   Download page does not have 
link to KEYS file
-   Unit tests fail on system 
dates later than 2009-12-31.
-   Log4cxx triggers locking 
inversion which can result in a deadlock.
+   Errors when 
compile log4cxx 0.10.0 under Win7 x64 with Visual Studio 2010 (due to Christian 
Boos and Feng Nan)
+   possibly wrong 
use of autotools docdir (due to Alex Zbarcea)
+   log4cxx doesn't 
compile on openembedded (due to Alex Zbarcea)
+   Console appender 
crashes if layout is not set
+   socketappendertestcase and xmlsocketappendertestcase not run
+   Bad link to 
log4cxx-dev archive
+   Eliminate 
anachronism warnings
+   Eliminate Extra 
";" ignored warnings
+   Local variables 
hide member variables
+   Add ability to 
compile out logging by logging level.
+   MDC::put will not 
overwrite existing key value pair
+   Apache log4cxx 
0.11.0 release
+   Headers cannot be 
included with very strict warning settings
+   AndFilter and 
others defined but not implemented
+   Reconnection not 
working for sockets
+   Threads for 
reconnecting sockets do not end cleanly when program exits
+   tests and sample 
code unnecessarily compiled during default make target
+   Sun Studio 11 
reports function hides base virtual

svn commit: r1556296 - /incubator/log4cxx/trunk/src/site/xdoc/usage.xml

[tschoening]

Author: tschoening
Date: Tue Jan  7 18:07:04 2014
New Revision: 1556296

URL: http://svn.apache.org/r1556296
Log:
Reduced paragraphs in definition lists because it looked to airy.

Modified:
incubator/log4cxx/trunk/src/site/xdoc/usage.xml

Modified: incubator/log4cxx/trunk/src/site/xdoc/usage.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/site/xdoc/usage.xml?rev=1556296&r1=1556295&r2=1556296&view=diff
==
--- incubator/log4cxx/trunk/src/site/xdoc/usage.xml (original)
+++ incubator/log4cxx/trunk/src/site/xdoc/usage.xml Tue Jan  7 18:07:04 2014
@@ -125,12 +125,9 @@ namespace log4cxx {
Level 
Inheritance
 

-   
-   The inherited 
level for a given logger
-   C, is equal to 
the first non-null level in the logger
-   hierarchy, starting at 
C and proceeding upwards in the
-   hierarchy towards the 
root logger.
-   
+   The inherited level 
for a given logger C, is equal to the
+   first non-null level in the 
logger hierarchy, starting at C and
+   proceeding upwards in the 
hierarchy towards the root logger.


 
@@ -321,11 +318,9 @@ LOG4CXX_WARN(logger, L"" << i <
Basic Selection 
Rule
 

-   
-   A log request of level 
p in a logger with
-   (either assigned or 
inherited, whichever is appropriate) level q, is enabled if  p >=
-   q.
-   
+   A log request of level p 
in a logger with (either assigned or
+   inherited, whichever is 
appropriate) level q, is enabled if
+   p >= q.


 
@@ -457,23 +452,14 @@ log4cxx::LoggerPtr y = log4cxx::Logger::
Appender Additivity
 

-   
-   The output of a log statement 
of logger C will
-   go to all the appenders in 
C and its ancestors. This is
-   the meaning of the term 
"appender additivity".
-   
-
-   
-   However, if an ancestor of 
logger C, say P,
-   has the additivity flag set to 
false, then
-   C's output will be 
directed to all the appenders in
-   C and it's ancestors 
upto and including P but
-   not the appenders in any of the 
ancestors of P.
-   
-
-   
-   Loggers have their additivity 
flag set to true by default.
-   
+   The output of a log statement of logger 
C will go to all the appenders
+   in C and its ancestors. This is 
the meaning of the term "appender
+   additivity". However, if an ancestor of 
logger C, say P, has the
+   additivity flag set to 
false, then C's output will be
+   directed to all the appenders in 
C and it's ancestors up to and
+   including P but, not the 
appenders in any of the ancestors of P.
+   
+   Loggers have their additivity flag set 
to true by default.


 

How to deal with broken links to apidocs?

[Thorsten Schöning]

Hello,

the documentation about how to use log4cxx contains some links to
classes in the apidocs folder, like the following:

> apidocs/classlog4cxx_1_1Logger.html#e3

Those links changed with the newer versions of doxygen to something
like the following:

> apidocs/classlog4cxx_1_1_logger.html#afc0e4d99cab7c38a2851d41e6edc1dee

The file name itself changed, 1_1Logger vs. 1_1_logger, and the anchor
is a md5 sum of the signature of the linked method, in this example
log4cxx::Logger::getRootLogger got linked. Whenever the signature of
the method changes, the anchor gets invalid until the link is updated
to the new id.

Does anyone has any experience with Doxygen regarding this kind of
"issue" or any clever idea how to deal with this? I may tent to don't
use ids in the links at all and hope that file names won't change that
often.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: How to deal with broken links to apidocs?

[Rhys Ulerich]

> Does anyone has any experience with Doxygen regarding this kind of
> "issue" or any clever idea how to deal with this? I may tent to don't
> use ids in the links at all and hope that file names won't change that
> often.

I think the filenames are fairly stable and would use them without hesitation.

Some Googling suggests that the hash is an MD5 of the method signature
and so it should be robust so long as the signature stays the same.

- Rhys

Re: How to deal with broken links to apidocs?

[Alexandru Zbarcea]

Generated code or generated documentation shouldn't be on the VCS
(subversion), right?

Christian, what is the best practice here in ASF?

There should be a script that updates the site with the latest
documentation, and this should be done by the Promotion step when we decide
a new version may be delivered. This is the reason of the automation task
using "nightly builds", using the #jenkins ASF etc.

What is your opinion on that? Should we consider from now on, as rule of
thumb, that NEVER we should put generated code on the VCS?

Regards,
Alex
On Jan 7, 2014 1:38 PM, "Thorsten Schöning"  wrote:

> Hello,
>
> the documentation about how to use log4cxx contains some links to
> classes in the apidocs folder, like the following:
>
> > apidocs/classlog4cxx_1_1Logger.html#e3
>
> Those links changed with the newer versions of doxygen to something
> like the following:
>
> > apidocs/classlog4cxx_1_1_logger.html#afc0e4d99cab7c38a2851d41e6edc1dee
>
> The file name itself changed, 1_1Logger vs. 1_1_logger, and the anchor
> is a md5 sum of the signature of the linked method, in this example
> log4cxx::Logger::getRootLogger got linked. Whenever the signature of
> the method changes, the anchor gets invalid until the link is updated
> to the new id.
>
> Does anyone has any experience with Doxygen regarding this kind of
> "issue" or any clever idea how to deal with this? I may tent to don't
> use ids in the links at all and hope that file names won't change that
> often.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme  http://www.AM-SoFT.de/
>
> Telefon...05151-  9468- 55
> Fax...05151-  9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>

Re: How to deal with broken links to apidocs?

[Rhys Ulerich]

> Generated code or generated documentation shouldn't be on the VCS
> (subversion), right?

Agreed.

Unless I'm mistaken, Thorsten is dealing with non-generated
documentation needing to link to generated documentation.

- Rhys

[jira] [Commented] (LOGCXX-417) Missing #include of breaks compilation on mac os 10.9

[Joseph Southwell (JIRA)]

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

Joseph Southwell commented on LOGCXX-417:
-

I just tried this on 10.8.5 with Xcode 5.0.2 and did not see the problem. I 
will update 10.9 tonight and see if it happens to me. Meanwhile, I have a 
couple of questions 

1. What version of Xcode were you using. What is the output of cc --version on 
your system?

2. It looks to me like atoi should come from stdlib.h which is included through 
the apr include files. What version of apr were you compiling with?

> Missing #include of  breaks compilation on mac os 10.9
> ---
>
> Key: LOGCXX-417
> URL: https://issues.apache.org/jira/browse/LOGCXX-417
> Project: Log4cxx
>  Issue Type: Bug
>Affects Versions: 0.10.0, 0.10.1
> Environment: Mac os 10.9
>Reporter: Daniel Russel
>Assignee: Joseph Southwell
> Fix For: 0.10.0, 0.10.1
>
>
> atoi isn't defined in stringhelper.cpp



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (LOGCXX-417) Missing #include of breaks compilation on mac os 10.9

[Daniel Russel (JIRA)]

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

Daniel Russel commented on LOGCXX-417:
--

Yes, this is something I just started seeing with 10.9. 

1. The compiler string is `Apple LLVM version 5.0 (clang-500.2.79) (based on 
LLVM 3.3svn)`

2. All the packages are via homebrew, which is currently at apr 1.5.0. That 
said, mac os seems to ship with an apr version of its own (at 
/usr/include/apr-1) but that is not explicitly used in the configure call.

> Missing #include of  breaks compilation on mac os 10.9
> ---
>
> Key: LOGCXX-417
> URL: https://issues.apache.org/jira/browse/LOGCXX-417
> Project: Log4cxx
>  Issue Type: Bug
>Affects Versions: 0.10.0, 0.10.1
> Environment: Mac os 10.9
>Reporter: Daniel Russel
>Assignee: Joseph Southwell
> Fix For: 0.10.0, 0.10.1
>
>
> atoi isn't defined in stringhelper.cpp



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: How to deal with broken links to apidocs?

[Thorsten Schöning]

Guten Tag Alexandru Zbarcea,
am Dienstag, 7. Januar 2014 um 20:24 schrieben Sie:

> There should be a script that updates the site with the latest
> documentation, and this should be done by the Promotion step when we
> decide a new version may be delivered.

As far as I understood the explanation about the project sites, the
site needs to be generated and afterwards committed to a special repo
to get published. We don't have access to that repo currently, I tried
and couldn't even read.

But as Rhys said, my "problem" currently is that we have manually
edited usage texts as part of the project site which links to
automatically generated apidocs contents and those targets may or may
not change unrecognized.

Maybe we are able to implement some logic in the build scripts to
finally create the links to the targets by searching the created files
in apidocs for some semi unique keys, but I'm currently not sure if
it's really worth the effort.

> This is the reason of the
> automation task using "nightly builds", using the #jenkins ASF etc. 

This wouldn't work right now for automatic publishment of the site
because we simply don't have access to the repo were the generated
sites are hosted. From my opinion we shouldn't focus on this anyways,
if we can use Jenkins to run useful tests that would be enough for
quite some time. Nightly builds which aren't used because of missing
user base or interest won't be of much help. :-)

> What is your opinion on that? Should we consider from now on, as
> rule of thumb, that NEVER we should put generated code on the VCS?

For easy things or those contents that are easy to generate, maybe
like the project site and apidocs currently, I agree. But if we don't
have a proper build process for some contents or it doesn't work for
some used platforms or compilers, we should decide case by case,
depending on needed space and all such stuff. Subversion is quite good
to even store binary data, I have some repos only for binary
distributions of our software for example and if it makes user's life
easier...

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

svn commit: r1556413 - /incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp

[joseph]

Author: joseph
Date: Wed Jan  8 00:48:19 2014
New Revision: 1556413

URL: http://svn.apache.org/r1556413
Log:
LOG4CXX-417: atoi undefined on macos 10.9

Modified:
incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp

Modified: incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp?rev=1556413&r1=1556412&r2=1556413&view=diff
==
--- incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp (original)
+++ incubator/log4cxx/trunk/src/main/cpp/stringhelper.cpp Wed Jan  8 00:48:19 
2014
@@ -30,6 +30,10 @@
 #include 
 #include 
 #include 
+//LOG4CXX-417: need stdlib.h for atoi on some systems.
+#ifdef APR_HAVE_STDLIB_H
+#include 
+#endif
 
 
 using namespace log4cxx;

[jira] [Commented] (LOGCXX-417) Missing #include of breaks compilation on mac os 10.9

[Joseph Southwell (JIRA)]

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

Joseph Southwell commented on LOGCXX-417:
-

The os provided apr results an error looking for apr_atomic.h so I am guessing  
you aren't using that.
Using apr 1.5 I was able to reproduce the problem. I fixed it a slightly 
different way than you. 
Can you update and verify that I fixed it for you as well?


> Missing #include of  breaks compilation on mac os 10.9
> ---
>
> Key: LOGCXX-417
> URL: https://issues.apache.org/jira/browse/LOGCXX-417
> Project: Log4cxx
>  Issue Type: Bug
>Affects Versions: 0.10.0, 0.10.1
> Environment: Mac os 10.9
>Reporter: Daniel Russel
>Assignee: Joseph Southwell
> Fix For: 0.10.0, 0.10.1
>
>
> atoi isn't defined in stringhelper.cpp



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [jira] [Commented] (LOGCXX-417) Missing #include of breaks compilation on mac os 10.9

[Daniel Russel]

You mean by building from the repo? Dumb question, but where is the repo?
The urls on 
don't work.


On Tue, Jan 7, 2014 at 4:49 PM, Joseph Southwell (JIRA) <
log4cxx-dev@logging.apache.org> wrote:

>
> [
> https://issues.apache.org/jira/browse/LOGCXX-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864927#comment-13864927]
>
> Joseph Southwell commented on LOGCXX-417:
> -
>
> The os provided apr results an error looking for apr_atomic.h so I am
> guessing  you aren't using that.
> Using apr 1.5 I was able to reproduce the problem. I fixed it a slightly
> different way than you.
> Can you update and verify that I fixed it for you as well?
>
>
> > Missing #include of  breaks compilation on mac os 10.9
> > ---
> >
> > Key: LOGCXX-417
> > URL: https://issues.apache.org/jira/browse/LOGCXX-417
> > Project: Log4cxx
> >  Issue Type: Bug
> >Affects Versions: 0.10.0, 0.10.1
> > Environment: Mac os 10.9
> >Reporter: Daniel Russel
> >Assignee: Joseph Southwell
> > Fix For: 0.10.0, 0.10.1
> >
> >
> > atoi isn't defined in stringhelper.cpp
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.1.5#6160)
>

svn commit: r1556432 - in /incubator/log4cxx/trunk: DISCLAIMER src/site/apt/index.apt

[rhys]

Author: rhys
Date: Wed Jan  8 03:13:46 2014
New Revision: 1556432

URL: http://svn.apache.org/r1556432
Log:
s/Podling-Name/log4cxx/g

Also, the TLP sponsor name was updated.

Modified:
incubator/log4cxx/trunk/DISCLAIMER
incubator/log4cxx/trunk/src/site/apt/index.apt

Modified: incubator/log4cxx/trunk/DISCLAIMER
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/DISCLAIMER?rev=1556432&r1=1556431&r2=1556432&view=diff
==
--- incubator/log4cxx/trunk/DISCLAIMER (original)
+++ incubator/log4cxx/trunk/DISCLAIMER Wed Jan  8 03:13:46 2014
@@ -1 +1 @@
-Apache Podling-Name is an effort undergoing incubation at The Apache Software 
Foundation (ASF), sponsored by the name of Apache TLP sponsor. Incubation is 
required of all newly accepted projects until a further review indicates that 
the infrastructure, communications, and decision making process have stabilized 
in a manner consistent with other successful ASF projects. While incubation 
status is not necessarily a reflection of the completeness or stability of the 
code, it does indicate that the project has yet to be fully endorsed by the ASF.
\ No newline at end of file
+Apache log4cxx is an effort undergoing incubation at The Apache Software 
Foundation (ASF), sponsored by Apache Logging Services. Incubation is required 
of all newly accepted projects until a further review indicates that the 
infrastructure, communications, and decision making process have stabilized in 
a manner consistent with other successful ASF projects. While incubation status 
is not necessarily a reflection of the completeness or stability of the code, 
it does indicate that the project has yet to be fully endorsed by the ASF.
\ No newline at end of file

Modified: incubator/log4cxx/trunk/src/site/apt/index.apt
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/site/apt/index.apt?rev=1556432&r1=1556431&r2=1556432&view=diff
==
--- incubator/log4cxx/trunk/src/site/apt/index.apt (original)
+++ incubator/log4cxx/trunk/src/site/apt/index.apt Wed Jan  8 03:13:46 2014
@@ -48,8 +48,8 @@ Short introduction to Apache log4cxx
 
 Disclaimer
 
-   Apache Podling-Name is an effort undergoing incubation at The Apache 
Software Foundation (ASF),
-   sponsored by the name of Apache TLP sponsor. Incubation is required of 
all newly accepted
+   Apache log4cxx is an effort undergoing incubation at The Apache 
Software Foundation (ASF),
+   sponsored by Apache Logging Services. Incubation is required of all 
newly accepted
projects until a further review indicates that the infrastructure, 
communications, and decision
making process have stabilized in a manner consistent with other 
successful ASF projects. While
incubation status is not necessarily a reflection of the completeness 
or stability of the code,

Re: project site and apidocs build again

[Rhys Ulerich]

Hi Thorsten,

> Could some of you please test the build? Something like "mvn clean
> site" should be enough.

It builds for me on Maven 3.0.4.  I tweaked the incubation statement
in r1556432.  Thanks for all the effort you put into getting the site
generation going.

- Rhys

[jira] [Updated] (LOGCXX-417) atoi undefined compiling stringhelper.cpp on mac os 10.9 Mavericks

[Joseph Southwell (JIRA)]

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

Joseph Southwell updated LOGCXX-417:


Summary: atoi undefined compiling stringhelper.cpp on mac os 10.9 Mavericks 
 (was: Missing #include of  breaks compilation on mac os 10.9)

> atoi undefined compiling stringhelper.cpp on mac os 10.9 Mavericks
> --
>
> Key: LOGCXX-417
> URL: https://issues.apache.org/jira/browse/LOGCXX-417
> Project: Log4cxx
>  Issue Type: Bug
>Affects Versions: 0.10.0, 0.10.1
> Environment: Mac os 10.9
>Reporter: Daniel Russel
>Assignee: Joseph Southwell
> Fix For: 0.10.0, 0.10.1
>
>
> atoi isn't defined in stringhelper.cpp



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [jira] [Commented] (LOGCXX-417) Missing #include of breaks compilation on mac os 10.9

[Joseph Southwell]

On Jan 7, 2014, at 8:17 PM, Daniel Russel  wrote:

> You mean by building from the repo? Dumb question, but where is the repo? The 
> urls on  don't work.
> 
Yeah, we moved to the incubator. Here is the new svn trunk url...
https://svn.apache.org/repos/asf/incubator/log4cxx/trunk
> 
> On Tue, Jan 7, 2014 at 4:49 PM, Joseph Southwell (JIRA) 
>  wrote:
> 
> [ 
> https://issues.apache.org/jira/browse/LOGCXX-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864927#comment-13864927
>  ]
> 
> Joseph Southwell commented on LOGCXX-417:
> -
> 
> The os provided apr results an error looking for apr_atomic.h so I am 
> guessing  you aren't using that.
> Using apr 1.5 I was able to reproduce the problem. I fixed it a slightly 
> different way than you.
> Can you update and verify that I fixed it for you as well?
> 
> 
> > Missing #include of  breaks compilation on mac os 10.9
> > ---
> >
> > Key: LOGCXX-417
> > URL: https://issues.apache.org/jira/browse/LOGCXX-417
> > Project: Log4cxx
> >  Issue Type: Bug
> >Affects Versions: 0.10.0, 0.10.1
> > Environment: Mac os 10.9
> >Reporter: Daniel Russel
> >Assignee: Joseph Southwell
> > Fix For: 0.10.0, 0.10.1
> >
> >
> > atoi isn't defined in stringhelper.cpp
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.1.5#6160)
> 

Joseph Southwell
jos...@southwell.org
The past is history,
The future's a mystery,
The present's a gift.




signature.asc
Description: Message signed with OpenPGP using GPGMail

[jira] [Created] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef

[Rhys Ulerich (JIRA)]

Rhys Ulerich created LOGCXX-419:
---

 Summary: 'typedef spi::KeySet KeySet' changes meaning of typedef
 Key: LOGCXX-419
 URL: https://issues.apache.org/jira/browse/LOGCXX-419
 Project: Log4cxx
  Issue Type: Bug
  Components: Filter
Affects Versions: 0.10.0, 0.10.1
 Environment: Ubuntu Saucy, GCC 4.8.1, Autotools
Reporter: Rhys Ulerich
Assignee: Rhys Ulerich


Observed in the build...

In file included from 
../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:24:0,
 from 
../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27,
 from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18:
../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:171:45: error: 
declaration of ‘typedef log4cxx::spi::KeySet 
log4cxx::spi::LoggingEvent::KeySet’ [-fpermissive]
 typedef spi::KeySet KeySet;
 ^
In file included from 
../../../../log4cxx/src/main/include/log4cxx/helpers/objectptr.h:21:0,
 from 
../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:21,
 from 
../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27,
 from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18:
../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:46:34: error: 
changes meaning of ‘KeySet’ from ‘typedef class 
std::vector > log4cxx::spi::KeySet’ [-fpermissive]
 LOG4CXX_LIST_DEF(KeySet, LogString);
  ^
../../../../log4cxx/src/main/include/log4cxx/log4cxx.h:48:55: note: in 
definition of macro ‘LOG4CXX_LIST_DEF’
 #define LOG4CXX_LIST_DEF(N, T) typedef std::vector N



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (LOGCXX-419) 'typedef spi::KeySet KeySet' changes meaning of typedef

[Rhys Ulerich (JIRA)]

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

Rhys Ulerich commented on LOGCXX-419:
-

This has bitten me in the past on GCC 4.6 
(https://red.ices.utexas.edu/issues/2971) where I have worked around it as 
demonstrated in 
https://github.com/RhysU/suzerain/blob/master/suzerain/support/logging.cpp 
using hackery like

// GCC 4.6.3 dislikes some Log4cxx constructs.  Mute -fpermissive to workaround.
// Warning-only idea taken from http://stackoverflow.com/questions/10932479
// The right thing to do is to fix log4cxx, but it seems to be a failed state.
//
// If relevant, push "GCC diagnostic warning -fpermissive"
#if ((__GNUC__ * 100) + __GNUC_MINOR__) >= 402
#pragma GCC diagnostic push
#pragma GCC diagnostic warning "-fpermissive"
#endif

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#if !defined(LOG4CXX)
#define LOG4CXX 1
#endif
#include 

// Matching pop for "GCC diagnostic warning -fpermissive"
#if ((__GNUC__ * 100) + __GNUC_MINOR__) >= 402
#pragma GCC diagnostic pop
#endif

> 'typedef spi::KeySet KeySet' changes meaning of typedef
> ---
>
> Key: LOGCXX-419
> URL: https://issues.apache.org/jira/browse/LOGCXX-419
> Project: Log4cxx
>  Issue Type: Bug
>  Components: Filter
>Affects Versions: 0.10.0, 0.10.1
> Environment: Ubuntu Saucy, GCC 4.8.1, Autotools
>Reporter: Rhys Ulerich
>Assignee: Rhys Ulerich
>
> Observed in the build...
> In file included from 
> ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:24:0,
>  from 
> ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27,
>  from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18:
> ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:171:45: 
> error: declaration of ‘typedef log4cxx::spi::KeySet 
> log4cxx::spi::LoggingEvent::KeySet’ [-fpermissive]
>  typedef spi::KeySet KeySet;
>  ^
> In file included from 
> ../../../../log4cxx/src/main/include/log4cxx/helpers/objectptr.h:21:0,
>  from 
> ../../../../log4cxx/src/main/include/log4cxx/spi/filter.h:21,
>  from 
> ../../../../log4cxx/src/main/include/log4cxx/filter/andfilter.h:27,
>  from ../../../../log4cxx/src/main/cpp/andfilter.cpp:18:
> ../../../../log4cxx/src/main/include/log4cxx/spi/loggingevent.h:46:34: error: 
> changes meaning of ‘KeySet’ from ‘typedef class 
> std::vector > log4cxx::spi::KeySet’ [-fpermissive]
>  LOG4CXX_LIST_DEF(KeySet, LogString);
>   ^
> ../../../../log4cxx/src/main/include/log4cxx/log4cxx.h:48:55: note: in 
> definition of macro ‘LOG4CXX_LIST_DEF’
>  #define LOG4CXX_LIST_DEF(N, T) typedef std::vector N



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Assigned] (LOGCXX-416) FileWatchdog thread crash on exit()

[Joseph Southwell (JIRA)]

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

Joseph Southwell reassigned LOGCXX-416:
---

Assignee: Joseph Southwell

> FileWatchdog thread crash on exit()
> ---
>
> Key: LOGCXX-416
> URL: https://issues.apache.org/jira/browse/LOGCXX-416
> Project: Log4cxx
>  Issue Type: Bug
>  Components: Configurator
>Affects Versions: 0.10.0
>Reporter: Jin Qing
>Assignee: Joseph Southwell
>Priority: Critical
>
> On exit(), FileWatchdog::checkAndConfigure() calls apr_pool_creae() and crash.
> Test code:
> #include 
> class A
> {
> public:
> A() {};
> ~A() {
> for (int i = 0; i < 100; i++)
>  for (int i = 0; i < 100; i++)
> ;
> }
> } g_a;
> int main()
> {
> log4cxx::xml::DOMConfigurator::configureAndWatch("log4j.xml", 1000);
> return 0;
> }
> After main() returned, but main  thread is still running, watchdog thread 
> will crash when checkAdnConfigure().



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: Contributor OS cross reference?

[Florian Seydoux]

On 06.01.2014 18:46, Joseph Southwell wrote:
> Should we have a cross reference somewhere
> 

I like the idea to have a kind of snapshot overview of the
Os/compiler-chain currently "available for[within] the team".

Doing this in the pom seems not a good idea, but, as suggested by Rhys
in a previous thread, we can maybe just use this thread to inform each
other.

Personally, I have currently access to:

OS Windows(seven x64)
- MinGW (msys), with gcc 4.5(.4) & 4.6(.4)
- Ms Visual studio 2010 (pro)
- Ms Visual studio express 2010 & 2013 (lower availability)
- Eventually: Cygwin + gcc 4.8.2

OS Debian (i386) [gcc/clang] <- even lower availability
(well... right now, my debian host is physically broken, but it will be
back soon).


flo

Re: setup Continuous Integration

[chand priyankara]

Hi Rhys,

Thanks.

I'll work on this issue.
Seems there is some code fix to be done, regrading a variable passing to a
function [missing const].

regards,


*Chand Priyankara*  [image: Facebook]
 [image: LinkedIn]  [image:
Blogger]  [image: Google
Plus]

|BSc(Eng) - Electrical & Information
|(094) 773-361-566
|ch...@engineering.com
|http://chandpriyankara.blogspot.com
sent via internet


On Wed, Jan 8, 2014 at 8:55 AM, Rhys Ulerich  wrote:

> > Can you please provide me a workaround to following error while building
> logcxx from current trunk:
> >
> > loggingevent.h:171:45: error: declaration of 'typedef
> log4cxx::spi::KeySet log4cxx::spi::LoggingEvent::KeySet' [-fpermissive]
>
> Is this using Autotools?  Or Ant?  If it's Autotools you can probably use
> CXXFLAGS=-fpermissive ./configure
> instead of the usual
>./configure
>
> I've had luck with this in the past:
> https://red.ices.utexas.edu/issues/2971
>
> I've filed https://issues.apache.org/jira/browse/LOGCXX-419 and will
> take a look at it.
>
> - Rhys
>

Re: Contributor OS cross reference?

[Thorsten Schöning]

Guten Tag Florian Seydoux,
am Mittwoch, 8. Januar 2014 um 05:57 schrieben Sie:

> I like the idea to have a kind of snapshot overview of the
> Os/compiler-chain currently "available for[within] the team".

Would it be worth documenting this on the project site instead of only
relying on this thread? We already have a menu item "Building" for
different platforms and could add something like "Used by the team" on
the same level. We wouldn't even necessarily need to mention names if
one doesn't want to, just a simple list or table like:

Member 1/Combination/whatever 1:

OS: ...
Compiler: ...

Member/Combination/whatever 2:

...

I have access to:

Windows 7 Ultimate x64
Embarcadero C++ Builder XE 4

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

svn commit: r1556458 - /incubator/log4cxx/trunk/src/site/xdoc/usage.xml

[tschoening]

Author: tschoening
Date: Wed Jan  8 07:46:21 2014
New Revision: 1556458

URL: http://svn.apache.org/r1556458
Log:
fixed links to apidocs

Modified:
incubator/log4cxx/trunk/src/site/xdoc/usage.xml

Modified: incubator/log4cxx/trunk/src/site/xdoc/usage.xml
URL: 
http://svn.apache.org/viewvc/incubator/log4cxx/trunk/src/site/xdoc/usage.xml?rev=1556458&r1=1556457&r2=1556458&view=diff
==
--- incubator/log4cxx/trunk/src/site/xdoc/usage.xml (original)
+++ incubator/log4cxx/trunk/src/site/xdoc/usage.xml Wed Jan  8 07:46:21 2014
@@ -75,9 +75,9 @@

 

-   Invoking the class static log4cxx::Logger::getRootLogger
+   Invoking the class static log4cxx::Logger::getRootLogger
method retrieves it. All other loggers 
are instantiated and retrieved with the class static
-   log4cxx::Logger::getLogger
+   log4cxx::Logger::getLogger
method. This method takes the name of 
the desired logger as a parameter. Some of the basic methods in the Logger
class are listed below.

@@ -111,7 +111,7 @@ namespace log4cxx {

Loggers may be assigned 
levels. The pre-defined
levels: TRACE, DEBUG, INFO, WARN, ERROR 
and FATAL are defined in the
-log4cxx::Level
+log4cxx::Level
class which provides accessor functions.

 
@@ -418,18 +418,18 @@ log4cxx::LoggerPtr y = log4cxx::Logger::
on their logger is only part of the picture. 
Log4cxx allows logging
requests to print to multiple destinations. In 
log4cxx speak, an output
destination is called an appender. 
Currently, appenders exist
-   for the console,
-   files, GUI
-   components, remote socket
-   servers,  NT Event 
Loggers, and remote UNIX
-   Syslog
-   daemons. It is also possible to log asynchronously.
+   for the console,
+   files, GUI
+   components, remote socket
+   servers,  NT Event 
Loggers, and remote UNIX
+   Syslog
+   daemons. It is also possible to log asynchronously.

 
More than one appender can be attached to a 
logger.
 

-   The addAppender
+   The addAppender
method adds an appender to a given logger.
 

@@ -442,7 +442,7 @@ log4cxx::LoggerPtr y = log4cxx::Logger::
is added to a logger, say C, then 
enabled logging requests for C and
C's children will print on a file 
and on the console. It is possible
to override this default behavior so that 
appender accumulation is no longer additive
-   by setting the additivity flag 
to
+   by setting
 the additivity flag to
false.

 
@@ -538,7 +538,7 @@ log4cxx::LoggerPtr y = log4cxx::Logger::

 

-   The PatternLayout, part
+   The PatternLayout, part
of the standard log4cxx distribution, lets the 
user specify the output
format according to conversion patterns similar 
to the C language
printf function.
@@ -659,11 +659,11 @@ void Bar::doIt() {
 }
 

-   The invocation of the BasicConfigurator::configure
+   The invocation of the BasicConfigurator::configure
method creates a rather simple log4cxx setup. 
This method is hardwired
-   to add to the root logger a 
+   to add to the root logger a 
ConsoleAppender. The output will be 
formatted using a
-   PatternLayout set
+   Pa