Have you compiled it with the autotools package at all? I *think*
that all you have to do is when you do the ./configure, you can do it
like the following:
CC=clang ./configure
and it will use clang instead of gcc.
-Robert Middleton
On Tue, Nov 7, 2017 at 5:51 AM, miguel angel rodriguez
Netbeans
and it built immediately as a maven project(although looking at the
POM it does look like it uses ant on the backend for some reason).
-Robert Middleton
On Fri, Nov 10, 2017 at 2:07 PM, Matt Sicker wrote:
> Release candidate available. Based on my experiences here, I think one of
> th
rogram that can read log files on your phone doesn't
make much sense to me, given the small screen size...
-Robert Middleton
On Sun, Nov 12, 2017 at 9:21 PM, Matt Sicker wrote:
> On 12 November 2017 at 20:10, Ole Ersoy wrote:
>
>> If you use it with PouchDB, localStorage, or
Not sure if it helps you at all, but I do have a branch that will
build with libapr(not apr2) that uses CMake if you want to try it out:
https://github.com/rm5248/logging-log4cxx/tree/cmake-updates
-Robert Middleton
On Thu, Jan 11, 2018 at 10:25 AM, James E. King, III wrote:
> Hello,
>
&g
o go about this is, or even if my help is needed.
There are some place where I as a user of log4cxx would like to see it
go, but I don't want to spend the time to implement updates/new
features if they're not going to be used.
-Robert Middleton
e
code; it sounds like the latter. It's not something that would be
practical for most projects.
-Robert Middleton
On Wed, Jan 24, 2018 at 7:45 PM, Matt Sicker wrote:
> I'm going to sum up my view here: if we split up repos to include plugins
> that depend on log4j-core, then w
The permissions seem to be wrong - I can't see the project without
logging into JIRA.
Also, should it go under the 'logging' category in JIRA?
-Robert Middleton
On Sat, Mar 10, 2018 at 1:45 AM, Matt Sicker wrote:
> https://builds.apache.org/job/Chainsaw/
> https://i
;m able to go to the website directly if I change it to go to
index.html instead:
https://logging.apache.org/log4cxx/latest_stable/index.html
-Robert Middleton
While it now shows up under the 'logging' category, I still can't see
the project at all unless I'm logged in. I'm assuming that's not
intentional.
-Robert Middleton
On Sun, Mar 11, 2018 at 7:05 PM, Matt Sicker wrote:
> This was fixed yesterday by the way.
Looks good to me. :)
-Robert Middleton
On Mon, Mar 12, 2018 at 10:49 AM, Matt Sicker wrote:
> Alright, permissions should match that of LOG4J2. Let me know if you're
> having any issues viewing it now.
>
> On 12 March 2018 at 09:11, Matt Sicker wrote:
>
>> This appe
...
I just had to do this the other day, not with a DMG builder but with
the maven-assembly-plugin. So I'm reasonably sure that this will work
as-is.
It should package t with: mvn -P osx-build package appbundle:bundle
-Robert Middleton
On Thu, Mar 15, 2018 at
Hey all, any updates on any releases for log4cxx? I know there was a
push a few months ago to try and get it out but I haven't heard
anything else since then.
-Robert Middleton
the memory pool and then calling the constructor
in-place(I have never done this before, but I know it is possible to
do). [1][2]. Or there may be some way to do it using a custom
allocator, that's something that I have never done either.
-Robert Middleton
[1]:
https://stackoverflow.co
multi process logging,
that's not a feature that I have ever used.
-Robert Middleton
On Mon, Nov 26, 2018 at 2:48 PM Sandhya Sundaresan <
sandhya.sundare...@esgyn.com> wrote:
> Hello again,
> Didn’t get any responses to my question below. Any log4cxx developers or
> users out
Niv,
log4cxx uses mostly APR(Apache Portable Runtime) on the backend, so as
long as APR is supported log4cxx may work. Most of the other stuff
that is supported should be conditionally compiled. I've never used
VxWorks before though, so I don't know what(if anything) works or
doesn&#
Build tooling meaning what exactly? Making it easy to include the
libraries in your application?
-Robert Middleton
On Tue, May 14, 2019 at 10:57 AM Matt Sicker wrote:
> I was speaking with Bill Rowe from httpd/apr the other day at
> ApacheCon Roadshow, and he's been working on
ling to help on this, but there's only so much that I can do
without being able to commit.
-Robert Middleton
[1]:
https://issues.apache.org/jira/browse/LOGCXX-486?focusedCommentId=16948277&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16948277
Hi all,
What's the bets way to contribute to log4cxx? There's a comment from
a few months ago on LOG4CXX-486[1], and not much has been done since
then. I'm willing to do the work to maintain log4cxx and do the
release, so what is the best way to become a contributor/comm
On Wed, Jan 1, 2020 at 10:52 AM Thorsten Schöning wrote:
>
> Guten Tag Robert Middleton,
> am Dienstag, 31. Dezember 2019 um 21:44 schrieben Sie:
>
> > [...]so what is the best way to become a contributor/committer?
>
> I suggest you start reading through the following do
> a release manager is a quick way to get invited to any ASF PMC :-)
>
I have been doing a lot of releases at work lately, so working on most
of the release process should be pretty straightforward for me to do.
I should be able to take a look at the (current) release scripts in
the next few days or so.
-Robert Middleton
oment a) how to do that, and b) if the Jenkins
instance there is configured properly in the first place. It seems
that Jenkins seems to be building only Java applications, while APR
and other C applications seem to be built on ci.apache.org. What's
the best way to help with this?
-Robert Middleton
also installing the proper dependencies.
-Robert Middleton
On Wed, Feb 19, 2020 at 6:53 PM Matt Sicker wrote:
>
> Some of the Jenkins nodes have Docker available which makes building
> simpler here.
>
> On Wed, Feb 19, 2020 at 17:49 Robert Middleton wrote:
>
> > I've cr
There's probably some way this could be improved, but unless
you actually profile and can point to a specific spot in the code
where a lot of time is being spent, it's probably not worth it to
change.
-Robert Middleton
On Tue, Mar 31, 2020 at 3:04 PM Norman Goldstein wrote:
>
> I
the exception and throw it.
-Robert Middleton
On Wed, May 6, 2020 at 3:43 PM Matt Sicker wrote:
>
> Potentially useful API update to look at here. Some sort of Logger that
> throws an exception with the log message instead?
>
> -- Forwarded message -
> Fr
zip and tar.gz here:
https://rm5248.com/log4cxx/
As of this point, do the zip/tar.gz files contain everything required for
release? Is there anything that needs to be added? I want to try and help
if there's something that's missing.
-Robert Middleton
character encodings like EBCDIC, which I have no idea if it
still works.
I would like to create a minimal library that depends solely on the
C++ standard library, but that would probably be easier with more
modern versions of C++(C++17 has filesystem library, C++20 introduces
formatting[3], which is p
So perhaps the best solution is based a little bit off of Stephen's
earlier PR(#18[1]), but instead of compiling out the code that depends
on gzip we make the test more granular(one test for rolling zip, one
test for rolling gz, etc) and disable[2] the test if the appropriate
executable is not found.
-Robert Middleton
[1]: https://github.com/apache/logging-log4cxx/pull/18
[2]: https://cmake.org/cmake/help/latest/prop_test/DISABLED.html
Does anything similar happen with log4j2?
-Robert Middleton
On Fri, Jul 17, 2020 at 6:57 AM Thorsten Schöning wrote:
>
> Guten Tag Robert Middleton,
> am Donnerstag, 16. Juli 2020 um 14:54 schrieben Sie:
>
> > So perhaps the best solution is based a little bit off of Stephen&#
the time on the QStrings.
Going through the currently open issues in JIRA, there's also a large
number that are either so old that they don't make much sense, or may have
been fixed already. Would it make sense to go through them at some point?
That's probably not something that I
ess somebody has a specific need to
use mysql this is almost certainly too old to be useful.
LOG4CXX-61 - Unless APR has database support(it doesn't seem too) this
should probably be closed
LOG4CXX-1 - I would say we should close this; any SMTP support may or
may not even work anymore
There are a bu
Thanks! I hope to be able to contribute to other logging projects as
well in the future(e.g. chainsaw).
-Robert Middleton
On Tue, Aug 4, 2020 at 5:35 PM Remko Popma wrote:
>
> Welcome, Robert!
>
> Remko.
>
>
>
> (Shameless plug) Every java main() method deserves http
night. Thorsten, are there any
other issues that you can think of that are critical? I'll also close
all of the issues that I put in my last email on feature proposals at
that time, unless you object to those.
-Robert Middleton
can import it into the logging KEYS file.
-Robert Middleton
efore. They /should/
be there in general, as that's the normal way to configure the
project(unless you are checking out the source code directly).
-Robert Middleton
On Mon, Aug 10, 2020 at 5:50 AM Thorsten Schöning
wrote:
> Guten Tag Robert Middleton,
> am Sonntag, 9. Aug
So I realize that I never set a normal time for this vote to be open, but
it has been 72 hours at this point. Do people still need more time to
validate, or are there some issues that need to be resolved first?
-Robert Middleton
On Mon, Aug 10, 2020 at 5:49 PM Remko Popma wrote:
> +1
>
with encoding, and possibly some other issues as well). At this point
that makes me much less confident in everything working properly, so
perhaps it is best to fix those issues first.
-Robert Middleton
On Wed, Aug 12, 2020 at 10:01 PM Ralph Goers
wrote:
> Yeah - ideally this would be done wit
ectly)
-Robert Middleton
On Mon, Aug 17, 2020 at 5:47 AM Stephen Webb wrote:
> I am using a recent version in production Ubuntu servers, so it is
> definitely release ready.
> +1
>
> On Mon, Aug 17, 2020, 7:27 PM Christian Grobmeier
> wrote:
>
> > Hello,
> >
> >
d,
as Thorsten uses a very old compiler. So would it make sense to have two
branches for development, the "legacy" 0.XX version and a new 1.XX version
that depends on (at least) C++11?
-Robert Middleton
On Sat, Aug 22, 2020 at 4:30 PM Stephen Webb wrote:
> I would completely support that
Since we have an actual release now, should we make an announcement email
on the gene...@logging.apache.org list? I can write up a blurb, but I'm
not sure who can post to that list.
I've also updated the tag for the release appropriately(v0.11.0)
-Robert Middleton
On Sun, Aug 23, 20
Something is funny with logging.apache.org - the links for log4cxx and
chainsaw lead to a 404 at the moment. I'm not sure if that's because
things are changing or if something else is messed up.
I assume this means now that the site will be committed to git instead of
svn?
-Robert Mid
the tests currently fails on OSX as well with a segfault, which is
the same thing that Ralph indicated a few weeks ago. I have an old mac
that I can try to reproduce it on, but if anybody has a chance sometime to
help debug this I would appreciate it.
-Robert Middleton
on to fail.
Fortunately, adding a .gitattributes file fixes this issue. I'll put that
up shortly, and then do a bigger PR with the github actions sometime soon,
hopefully with the OSX crash fixed.
-Robert Middleton
On Mon, Sep 7, 2020 at 3:23 AM Thorsten Schöning
wrote:
> Guten Tag Robert Middl
site can't use a subdirectory from the
main repository).
Thoughts?
-Robert Middleton
everything over yet(and there's still some
formatting to fix), but at a minimum the main
page, changelog, dependencies, and FAQ page should work. The usage
page is there, but a lot
of the formatting is missing at the moment. The page links on the
left can be reordered somehow and given
drop-downs like the entries for 'Classes' to match closer with maven.
-Robert Middleton
something about
log4j2 supporting GELF a while ago - perhaps that could be a good
standard for sending log messages?
-Robert Middleton
On Sat, Nov 7, 2020 at 12:27 PM Matt Sicker wrote:
>
> Any use of deserialization over the network (or from untrusted input
> sources in general) sh
ed as well, but I haven't
used it enough to know where to start.
-Robert Middleton
On Sat, Nov 7, 2020 at 5:49 PM Scott Deboy wrote:
>
> If I recall correctly, log4cxx supports the log4j xml format over tcp.
>
> Scott
>
> On Sat, Nov 7, 2020, 11:49 AM Matt Sicker wro
ave a lot of spam in it, along with the
LOGGINGLOG4J and LOGGINGLOG4PHP wikis. Is there any reason for us to
keep the wiki around? They don't seem to be used at all.
-Robert Middleton
les to the correct place, so I
don't see it being a big issue to do manually.
Thoughts?
-Robert Middleton
[1]:
https://github.com/apache/logging-log4cxx/blob/beb771eae0d7e8ee40067a969d8199ab9639982e/src/site/xdoc/usage.xml#L78
e a few JIRA issues for that so I don't forget them.
-Robert Middleton
On Sat, Dec 26, 2020 at 3:44 PM Thorsten Schöning wrote:
>
> Guten Tag Robert Middleton,
> am Samstag, 26. Dezember 2020 um 19:10 schrieben Sie:
>
> > Thoughts?
>
> Do you really think the chan
er of new features / standard library classes that are in the new
standards that are very useful.
I also have a separate branch for the documentation updates, which
should be ready at this point.
-Robert Middleton
On Wed, Dec 30, 2020 at 3:03 AM Thorsten Schöning wrote:
>
> Guten Tag Robert Mid
to make it easier to do releases
* I have a prototype of using updated standard C++ libraries(C++11 and
better), but that hasn't been merged in yet
-Robert Middleton
On Tue, Feb 9, 2021 at 12:40 PM Matt Sicker wrote:
> Over the past year or two, I've been working to include more
xx on their code. Somebody was asking about this a
while ago, but now I can't remember where they were asking about it.
PR available here: https://github.com/apache/logging-log4cxx/pull/53
-Robert Middleton
on?), you'll get
an error. On Linux, this isn't the case - unless you explicitly lock
the file, it's available for everybody. You can happily delete a file
on Linux, and the FD that you can read/write to won't become invalid,
even if you can't open it anymore on the files
plifies some code - as you saw, I left in some
std::shared_ptrs around instead of log4cxx::pointer, but the code that
detects for C++ wouldn't be needed if we can assume that it already
exists(some detection code for C++14/17 features would still be
required).
-Robert Middleton
that depends
on LoggerPtr though, so I would be fine just typedef-ing the pointers
with the macros that we have now, but permanently typedef-ing to
std::shared_ptr(no utilization of boost fallback behavior).
-Robert Middleton
[1]: https://yarchive.net/comp/linux/typedefs.html
Sounds good. I'll update that in the coming days/weeks - I have a
deadline approaching for work, so I may not be able to do much for a
bit.
I'll also assume that other C++11 features are available(e.g.
std::thread, enhanced for loop) moving forward.
-Robert Middleton
On Tue, Mar 2,
.
-Robert Middleton
On Thu, Mar 4, 2021 at 4:04 AM Thorsten Schöning wrote:
>
> Guten Tag Robert Middleton,
> am Donnerstag, 4. März 2021 um 00:46 schrieben Sie:
>
> > Sounds good. I'll update that in the coming days/weeks - I have a
> > deadline approaching for work, so I m
bmier), or
is that a PMC-level activity?
-Robert Middleton
I've switched over to using the rmiddleton account, since that's tied to
the ASF LDAP.
I think Steven Webb is also a committer, although I haven't seen him around
much.
-Robert Middleton
On Wed, Mar 10, 2021 at 10:47 PM Ralph Goers
wrote:
> I don’t even see you as a commit
Hmm.. that doesn't seem to have changed anything on my side.
-Robert Middleton
On Thu, Mar 11, 2021 at 10:40 PM Ralph Goers
wrote:
> Your user is now a committer on the Logcxx project in Jira. There are
> multiple users in Jira named Stephen Webb so I will need confirmation of
>
According to Adopt OpenJDK[1], version 8 will be supported until at least
May 2026, while Java 11 will be supported until at least October 2024.
That obviously doesn't affect Java 7, but it may affect any plans as to
when Java 8 will be dropped.
-Robert Middleton
[1]: https://adoptopenjd
- there's a lot of code that would need to be changed, but it's not
particularly hard.
-Robert Middleton
s still some documentation that I want to make
sure is updated. That should also give it a period of time to allow
for any new bug(s) to be reported. I have some applications on my
side as well that I'll compile with and make sure that they still work
correctly.
-Robert Middleton
Before I go and do a release of log4cxx, are there any issues that may
need to be taken care of before the next release? Otherwise, if there
are no objections, I'll call for a release vote here shortly for
version 0.12.0.
-Robert Middleton
_DIR} in src/main /include and src/main/cpp.
Apparently also in the Doxyfile.in as well - do you know what the
correct variable should be? It looks like we may want to use
PROJECT_SOURCE_DIR instead, if we can't do absolute paths. Or maybe
we just need something like LOG4CXX_SOURCE_DIR?
-Robert Middleton
Also, question for Thorsten: are you comfortable closing PR #22 at
this point? There's been no activity on it for a year at this point,
and it seems like the resolution we came up with was "don't do
anything".
-Robert Middleton
On Wed, Apr 14, 2021 at 9:27 PM Rob
If you're able to test the PR that I just did, that would be helpful:
https://github.com/apache/logging-log4cxx/pull/63
All of the tests pass so it's probably good, but an extra set of eyes
is helpful.
-Robert Middleton
On Thu, Apr 15, 2021 at 4:32 AM Stephen Webb wrote:
>
> &g
Does anybody happen to have a known good XML file for rollover with
compression? I'm working on LOGCXX-523 and I'm trying to configure
the XML file to gzip the files when rolling over, but I can't get it
to work. It seems that the only configuration that we have in the
tests programmatically conf
k about removing it post
0.12.
The quirky thing about this is that because log4cxx doesn't actually
care about the Java class name, the following lines in the config file
are all equivalent:
-Robert Middleton
On Sat, Apr 17, 2021 at 4:27 AM Thorsten Schöning wrote:
>
> Guten Tag
t
everything beyond the last '.' to load the class:
https://github.com/apache/logging-log4cxx/blob/79352bd0160866d06b61414f2dc83d1f71b44335/src/main/cpp/class.cpp#L123
Since all of the examples that I gave end in 'RollingFileAppender' and
they don't equal "org.apache.log4j.RollingFileAppender", the correct
RollingFileAppender is used.
-Robert Middleton
have shared_ptrs of different types pointing at the
same object).
-Robert Middleton
On Wed, Apr 21, 2021 at 2:52 AM Stephen Webb wrote:
> Hi Robert,
>
> I suggest adding the following to 'change-report-gh.md'
>
>
> Migrating from 0.11.0
> ---
about that.
-Robert Middleton
On Thu, Apr 22, 2021 at 3:46 AM Stephen Webb wrote:
> Yes, your fancy new cast function looks like a better approach.
>
> Should the note mention it uses the aliasing constructor std::shared_ptr or
> is it always going to be safe with log4cxx::Object poi
apache.org/log4cxx/next_stable/
Distribution archives:
https://dist.apache.org/repos/dist/dev/logging/log4cxx/
Building directions are on the website(under 'Development'). Note that APR
is required to build(as well as boost if your compiler does not support
C++17).
-Robert Middleton
rsten.
-Robert Middleton
On Tue, Apr 27, 2021 at 10:32 PM Stephen Webb wrote:
> +1
>
> I built and used it with the systems I maintain and everything looks good.
>
> On Tue, Apr 27, 2021 at 11:44 AM Robert Middleton
> wrote:
>
> > This is a vote to release log4cxx 0.12.
ur compiler does
not support C++17).
Changes since RC1:
* Fixed build with GCC-11
* Removed ABI file from release tarball, since that is really not
interesting to most end-users
* Ignored a few files that were incorrectly added to release
tarball(*.swp, CMakeLists.txt.user)
* Added release date on changelog(now 2021-05-01)
-Robert Middleton
I honestly don't know how important these warnings are - I don't do
much on Windows. As far as I'm aware the declspec should be #defined
correctly, could that have something to do with it?
-Robert Middleton
On Mon, May 3, 2021 at 2:20 PM Patrick Mills
wrote:
>
> Anyone
I've updated the NOTICE file in git, so it will be correct for the
next release. :)
Otherwise everything still looks good to me, so adding my +1 now.
-Robert Middleton
On Mon, May 3, 2021 at 2:02 PM Matt Sicker wrote:
>
> If you don't feel the NOTICE file is a problem, then
chainsaw.
Side note, the Jenkins build fails for chainsaw at the moment - I'm
not sure who takes care of that either.
-Robert Middleton
can review merge requests.
Those changes cause it to crash on Linux at least, due to it not
supporting the integration, so I wanted to fix that. There are also a
few UI changes so that it will let you see what you're typing.
-Robert Middleton
On Sat, May 8, 2021 at 2:30 PM Matt Sicker
As a reminder, this vote is still outstanding.
-Robert Middleton
On Tue, May 4, 2021 at 7:10 PM Robert Middleton wrote:
>
> I've updated the NOTICE file in git, so it will be correct for the
> next release. :)
>
> Otherwise everything still looks good to me, so adding my
This vote has passed with binding +1 votes from Matt Sicker, Robert
Middleton, Remko Popma and Ralph Goers, with non-binding +1 votes from
Thorsten Schöning and Steven Webb.
I will proceed with the release.
-Robert Middleton
On Sun, May 9, 2021 at 12:36 AM Ralph Goers wrote:
>
> +1
>
;git clone
https://github.com/apache/logging-chainsaw.git"; and then "git checkout
tags/apache-chainsaw-2.1.0-RC1"
Web site: https://logging.staged.apache.org/chainsaw/2.1.0/
Distribution archives: https://dist.apache.org/repos/dist/dev/logging/chainsaw/
-Robert Middleton
he sources. It looks like we might be missing something in the POM?
The current directions for releasing make no mention of the sources,
and the sign-artifacts.sh doesn't seem to attempt to sign the sources
either.
-Robert Middleton
On Wed, Jun 2, 2021 at 8:40 AM Gary Gregory wrote:
>
> On
Does that mean we can now say log4j2 is out of this world? ;)
-Robert Middleton
On Fri, Jun 4, 2021 at 11:47 AM Gary Gregory wrote:
>
> -- Forwarded message -
> From: Gary Gregory
> Date: Fri, Jun 4, 2021, 11:27
> Subject: Apache Log4j is part of the Mars
I'm working on that now. I'm just fixing the copyright date in the
NOTICE file and making sure that the sign-artifacts will sign the
source archive, so just a few minor changes.
-Robert Middleton
On Sat, Jun 5, 2021 at 8:11 PM Ralph Goers wrote:
>
> Is something going to be don
aw-2.1.0-RC2"
Web site: https://logging.staged.apache.org/chainsaw/2.1.0/
Distribution archives: https://dist.apache.org/repos/dist/dev/logging/chainsaw/
-Robert Middleton
ns instead).
-Robert Middleton
On Sun, Jun 6, 2021 at 3:54 PM Matt Sicker wrote:
>
> I've fixed this issue. The problem was that while the version in master
> doesn't have a -SNAPSHOT, it can't be deployed to the snapshots repository
> (duh). I've updated the pipel
You need to send a message to dev-unsubscr...@logging.apache.org
Mailing list info is here: http://logging.apache.org/mailing-lists.html
-Robert Middleton
On Mon, Jun 7, 2021 at 8:47 AM Palmer, Eric wrote:
>
> How can I get my email address remove from dev@logging.apache.org
Adding my +1 here.
With that, the release passes with +1 votes from Remko Popma, Matt
Sicker, and Robert Middleton.
I shall proceed with the release.
-Robert Middleton
On Sun, Jun 6, 2021 at 3:22 PM Matt Sicker wrote:
>
> Nits (not blockers, but useful to fix for next release):
>
that this would make the most sense to have
Chainsaw listen on a TCP or UDP port for the JSON messages. Are there
any other ways that you would normally send a log message that I'm not
thinking about?
-Robert Middleton
,
the ECS documentation seems to be very concerned with how to use
elastic search, but not with how to actually format the messages to
send.
-Robert Middleton
ng it into the
Log4j1 format.
This does require adding a new dependency to parse JSON(Genson), but
that is Apache licensed.
-Robert Middleton
On Sat, Jun 19, 2021 at 6:29 AM Volkan Yazıcı wrote:
>
> For the records, JsonTemplateLayout also quotes all escape characters,
> including CR an
try
compiling src/cmake/boost-fallback/test-boostsharedmutex.cpp and see
if it fails. If it compiles properly, there may just be a bug with
the detection of boost. Otherwise perhaps boost isn't compiled with
needed support for shared_mutex?
-Robert Middleton
On Thu, Jun 24, 2021 at 4:59 PM Miranda, R
C_PER_SEC * waitFactor);
}
}
The issue seems to be that due to various scheduling whims, we may not
always get the correct number of messages printed out per second, so
the test will fail. Is there a better way to do this, perhaps
something in log4j?
-Robert Middleton
ular scheduling and sleep interaction.
I'm thinking that the best thing to do is to change up the algorithm
slightly so that it does
* write log line 1
* write log line 2
* wait until the next second
* write log line 3, causing rollover
etc...
-Robert Middleton
On Thu, Jul 1, 2021 at 3
That does sound like a good idea. We can probably replace all of the calls
to APR for the time with their C++ standard equivalents as well to allow
for easy mocking.
-Robert Middleton
On Mon, Jul 5, 2021 at 3:26 AM Volkan Yazıcı
wrote:
> I totally agree with Matt on this. Once the code sta
Without the fix for LOGCXX-534, multithreaded rolling logging is
broken. Since it's a pretty simple and minor fix, I was thinking
that we should do a release with just this fix, as this seems like it
could be a common configuration. Thoughts?
-Robert Middleton
I'll do a release sometime in the next week or two then,
cherry-picking that one commit. It shouldn't be that hard to do.
-Robert Middleton
On Mon, Sep 13, 2021 at 10:00 AM Thorsten Schöning
wrote:
>
> Guten Tag Robert Middleton,
> am Montag, 13. September 2021 um
ise
I expect this to be what is released for 12.1. I'll do the proper
release in a day or so, unless something else comes up that we feel is
needed for this release.
-Robert Middleton
On Mon, Sep 13, 2021 at 5:43 PM Robert Middleton wrote:
>
> I'll do a release sometime in the
ist.apache.org/repos/dist/dev/logging/log4cxx/
Building directions are on the website(under 'Development'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
1 - 100 of 245 matches
Mail list logo
