[
https://issues.apache.org/jira/browse/LOGCXX-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning updated LOGCXX-421:
-
Attachment: XE 4.zip
I've attached my current projects for Embarcadero C++ Builder XE 4 in
[
https://issues.apache.org/jira/browse/LOGCXX-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Schöning closed LOGCXX-444.
Resolution: Duplicate
This is a known issue and won't get fixed any time soon, it's just to
whamma created LOGCXX-444:
-
Summary: how to build on c++ builder.
Key: LOGCXX-444
URL: https://issues.apache.org/jira/browse/LOGCXX-444
Project: Log4cxx
Issue Type: Wish
Components: Build
Guten Tag Rhys Ulerich,
am Dienstag, 21. Oktober 2014 um 14:14 schrieben Sie:
> Beyond LOG4CXX-428 (which I'll do this week), what
> development/bugfixes/JIRAs must be addressed in 0.11.0?
We have only a few "officially" scheduled currently and LOGCXX-441
seems worth unscheduling to me. On the ot
[
https://issues.apache.org/jira/browse/LOGCXX-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178330#comment-14178330
]
Rhys Ulerich commented on LOGCXX-442:
-
As I'm not familiar with that portion of the co
Hi all,
I've crawled out from under my rock (dissertation completed,
postgraduate job started, settled in new city). It would be good to
get 0.11.0 out the door by end of November.
Beyond LOG4CXX-428 (which I'll do this week), what
development/bugfixes/JIRAs must be addressed in 0.11.0?
If ther
Author: rhys
Date: Tue Oct 21 12:07:24 2014
New Revision: 1633356
URL: http://svn.apache.org/r1633356
Log:
LOG4CXX-443: Return by const reference in Logger::getName()
Modified:
incubator/log4cxx/trunk/src/changes/changes.xml
incubator/log4cxx/trunk/src/main/include/log4cxx/logger.h
Modif
[
https://issues.apache.org/jira/browse/LOGCXX-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rhys Ulerich resolved LOGCXX-443.
-
Resolution: Fixed
Fix Version/s: 0.11.0
Fixed in r1633356, including changelog update
> Re