mko.po...@gmail.com> wrote:
>
> I thought Gary needed a way to detect that the specified location didn't
> work. But perhaps a warning message is sufficient.
>
> Sent from my iPhone
>
> On Apr 12, 2017, at 10:05, Ralph Goers <ralph.go...@dslextreme.com
> <ma
I'd prefer an error message but then have it continue with the current behavior.
Sent from my iPhone
> On Apr 11, 2017, at 5:47 PM, Remko Popma wrote:
>
> I can see both sides of the argument.
>
> Rather than changing the semantics of the existing method, what about
[
https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-239.
--
> RollingFileAppender should support logging directly to the file referenced in
> the fileP
[
https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-239.
Resolution: Fixed
Fix Version/s: 2.8
> RollingFileAppender should support logging direc
1. Perform the release build.
2. Build the site.
3. Upload the site to where we can view it.
4. Vote on it.
5. When it passes upload the site to a directory adjacent to the log4j2 site
directory. Something like log4j-scala/log4j-scala-11.0.
Once you have that we can modify the links in the
[
https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964851#comment-15964851
]
Ralph Goers commented on LOG4J2-1185:
-
You have to omit the fileName attribute entirely. The rolling
[
https://issues.apache.org/jira/browse/LOG4J2-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-1875.
---
> Filtering Exceptions on Log4J 1.X
> -
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1875.
-
Resolution: Invalid
This Jira is for Log4J 2 issues only.
> Filtering Exceptions on Log4J
ne.com> wrote:
>
> Is it this repo? git://git.apache.org/logging-log4j-tools.git
> <http://git.apache.org/logging-log4j-tools.git>
>
> It is currently empty (except two text files). I don't feel confident to do
> the initial setup of the repository.
>
> On Mo
Maybe, but if it is large enough I would just migrate it from svn to its own
git repo.
Ralph
> On Apr 10, 2017, at 9:05 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
>
> Is this where a Chainsaw refresh would live?
>
> Gary
>
> On Apr 10, 2017 9:01
le. Maybe this new module can be moved to
> log4j2-tools repo.
>
> On Mon, Apr 10, 2017 at 5:48 PM, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> I created a new git repo for log4j2-tools. We should not create any more
> module
I created a new git repo for log4j2-tools. We should not create any more
modules if we can avoid it.
Ralph
> On Apr 10, 2017, at 7:28 AM, Remko Popma wrote:
>
> I guess this is a matter of preference but we already have a lot of modules.
> Having one for all standalone
e 2.8.1 logo since that was the release artifact
> technically. If you don't see the new logo on the site, it's probably a
> caching issue.
>
> On 9 April 2017 at 13:52, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> Thanks, but y
lly. If you don't see the new logo on the site, it's probably a
> caching issue.
>
> On 9 April 2017 at 13:52, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> Thanks, but you used the 2.8.1 logo instead of 2.8.2.
>
> Oh darn,
Thanks, but you used the 2.8.1 logo instead of 2.8.2.
Oh darn, I just noticed the web site wasn’t updated either. I guess I will
have to fix that.
Ralph
> On Apr 8, 2017, at 4:36 PM, Remko Popma wrote:
>
> Blogged:
tem 10 on this list was recently fixed.
Ralph
> On Apr 7, 2017, at 12:04 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> I just took a look at the list. I don’t see the response that points to
> bugzilla.
>
> In your comment you mentioned that Log4j provides an api but
re) convoluted than the JCP.
>
> On 6 April 2017 at 19:41, Gary Gregory <garydgreg...@gmail.com
> <mailto:garydgreg...@gmail.com>> wrote:
> A quick review of the document appears to have SLF4J as a requirement. Shame
> about that.
>
> Gary
>
> On Thu,
We will have to modify log4j-slf4j-impl to support the new binding mechanism. I
know it uses service loader but I haven’t looked at the details. I looked at
service loader when I created the binding between our api and core but decided
not to use it because I wanted to also include the logic to
Where does one comment on these?
The problem is that they mention Java 8 support, but SLF4J doesn’t take
advantage of any Java 8 features yet. No support for Lamda’s. From what I am
seeing the next release will support running in Java 9 and will leverage
StackWalker and support Java modules
to use?
Ralph
> On Apr 5, 2017, at 7:01 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> Why?
>
> Ralph
>
>> On Apr 5, 2017, at 6:56 AM, Mikael Ståldal <mikael.stal...@magine.com
>> <mailto:mikael.stal...@magine.com>> wrote:
>>
&g
Why?
Ralph
> On Apr 5, 2017, at 6:56 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote:
>
> I see. But couldn't it be a bit confusing for users to have both?
>
> On Wed, Apr 5, 2017 at 3:54 PM, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...
I’m not sure I understand the question. Have you looked at the code? The
syslog appender is nothing more than the SocketAppender hardwired to use one of
those two layouts. However, there is nothing preventing someone from using
those Layouts with a different appender.
Ralph
> On Apr 5,
the ring buffer go away if the JVM goes
> down?
>
> Ideally I want to publish and forget, with the publish part asynchronous,
> call the API, and it returns right away.
>
> Is there no way to do that with our JMS Appender?
>
> Gary
>
> On Mon, Apr 3, 2017 at 5:3
no way to do that with our JMS Appender?
>
> Gary
>
> On Mon, Apr 3, 2017 at 5:38 PM, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> What’s the point though when all you have to do is specify the pattern layout
> with “%m%ex{
What’s the point though when all you have to do is specify the pattern layout
with “%m%ex{none}”?
How can you do auditing with the async logger? You may lose events with that.
Your use case is exactly why I wrote the FlumeAppender. It is very much like
JMS but a whole lot faster and guarantees
l.com
> <mailto:boa...@gmail.com>> wrote:
> No, I figured I'd do log4j-core first. Still working on that right now, had
> to restart the build from the tag because a test randomly decided to fail at
> the worst possible time.
>
> On 2 April 2017 at 15:11, Ralph Goers <
Where have you been? I posted performance benchmarks based on that a week or
two ago. See all my updates to LOG4J2-1359.
I have already implemented StackWalker support on branch java9NoMultiRelease. I
started on a branch for LOG4J2-1359 but trouble with the Multi-Release jar made
me rethink
rst release. I did
> remember to update that before making the RC.
>
> On 2 April 2017 at 16:24, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> Oh. I just saw the release vote email. You should have done this before you
> ran
Oh. I just saw the release vote email. You should have done this before you ran
the release build. It isn’t a showstopper though.
Ralph
> On Apr 2, 2017, at 2:22 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> I believe I follow the same process as Gary. In src/site/res
I believe I follow the same process as Gary. In src/site/resources/logo you
will find a bunch of logo’s that Gary generated. All the ones that have been
used have a version numbered image. I just pick the next one I like and edit it
in gimp and add the version number.
If you are unable to do
Has a Scala release been performed? The site needs to be deployed before I can
modify the log4j page(s) to point to it.
Ralph
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail:
I have created a logging channel on Slack for anyone who wants to use it.
Ralph
> Begin forwarded message:
>
> From: "John D. Ament"
> Subject: Slack Invites
> Date: March 29, 2017 at 6:54:53 AM MST
> To: "gene...@incubator.apache.org"
>
[
https://issues.apache.org/jira/browse/LOG4J2-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1859.
-
Resolution: Not A Problem
This is working as designed. The fileName is indeed a file name
Matt,
Any update on this?
Ralph
> On Mar 21, 2017, at 10:27 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> Thanks Matt!
>
> Ralph
>
>> On Mar 21, 2017, at 10:15 AM, Matt Sicker <boa...@gmail.com
>> <mailto:boa...@gmail.com>> wrote
[
https://issues.apache.org/jira/browse/LOG4J2-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-1833:
---
Assignee: Ralph Goers
> NullPointerException using fileName property of RollingF
[
https://issues.apache.org/jira/browse/LOG4J2-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943496#comment-15943496
]
Ralph Goers commented on LOG4J2-1833:
-
While this error needs to be fixed, the result of the fix
Thanks Matt!
Ralph
> On Mar 21, 2017, at 10:15 AM, Matt Sicker <boa...@gmail.com> wrote:
>
> No other opinions apparently. I suppose we'll go with the single list with
> bounce messages. I'll follow up with infra later today.
>
> On 18 March 2017 at 13:1
OSGi in general
> despite one of the leading OSGi spec leads being on the Jigsaw project.
>
> On 16 March 2017 at 08:37, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> Nevermind. I moved the dependency plugin after the
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931946#comment-15931946
]
Ralph Goers commented on LOG4J2-1359:
-
In the issue for the Maven bundle plugin it was suggested we
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931936#comment-15931936
]
Ralph Goers edited comment on LOG4J2-1359 at 3/19/17 8:27 PM:
--
Here
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931936#comment-15931936
]
Ralph Goers commented on LOG4J2-1359:
-
Here are the results of the benchmarks. Overall, it seems
[
https://issues.apache.org/jira/browse/LOG4J2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931827#comment-15931827
]
Ralph Goers commented on LOG4J2-1746:
-
As part of implementing support for StackWalker a Jenkins Java
[
https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931825#comment-15931825
]
Ralph Goers commented on LOG4J2-1745:
-
In order to implement support for StackWalker support
[
https://issues.apache.org/jira/browse/LOG4J2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-1746:
---
Assignee: Ralph Goers
> Add JDK9 build to Jenk
[
https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-1745:
---
Assignee: Ralph Goers
> Add support for multi-release jars for J
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931455#comment-15931455
]
Ralph Goers commented on LOG4J2-1359:
-
I have created branch LOG4J2-1359. To build Log4j you must
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931455#comment-15931455
]
Ralph Goers edited comment on LOG4J2-1359 at 3/18/17 11:05 PM:
---
I have
Thanks
>
> On 16 March 2017 at 22:23, Matt Sicker <boa...@gmail.com
> <mailto:boa...@gmail.com>> wrote:
> Oh, I didn't realise I had a response on how to handle that. Let me follow up
> with infra.
>
> On 16 March 2017 at 21:46, Ralph Goers <ralph.go...@dsl
Is there any follow-up to this?
Ralph
> On Mar 12, 2017, at 9:30 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> 1. That seems fine to me.
> 2. Is it possible to do both? I like the idea of annoying the sender but
> still allowing the email to be sent. It would
017, at 11:36 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> I have built the Java 9 code. Now I am copying the classes into the log4j-api
> jar. They have to be placed at META-INF/versions/9. However, when I do this I
> am getting an error from the Maven bund
=org.apache.logging.log4j.util.ClassPredicate,
META-INF/versions/9/org/apache/logging/log4j/util/ClassNamePredicate.class=org.apache.logging.log4j.util.ClassNamePredicate}
[ERROR] Error(s) found in manifest configuration
Any idea on how to get around this?
Ralph
> On Mar 15, 2017, at 9:14 AM, Ralph Go
it is released
then be playing catch-up.
Ralph
> On Mar 15, 2017, at 8:38 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote:
>
> It would be bad to require Java 9 to build the main project as long as Java 9
> is not released.
>
> On Wed, Mar 15, 2017 at 4:27 P
st of
> the project locally with JDK 1.7 or 1.8 as I doubt everyone wants to install
> JDK 9 on all their development machines while it's still in beta.
>
> On 15 March 2017 at 10:07, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>
I know how to implement the StackWalker code but I don’t quite know how to get
it into the build. The main build needs to keep using Java 7 but of course the
StackWalker stuff needs to be compiled with Java 9. Technically, I know how I
could do that except I have no idea how it would work in
[
https://issues.apache.org/jira/browse/LOG4J2-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926313#comment-15926313
]
Ralph Goers commented on LOG4J2-1849:
-
Neither is Arizona so I wouldn't see the problem either
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924922#comment-15924922
]
Ralph Goers edited comment on LOG4J2-1359 at 3/14/17 8:27 PM:
--
It would
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924922#comment-15924922
]
Ralph Goers commented on LOG4J2-1359:
-
It would be a direct replacement for the method
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923621#comment-15923621
]
Ralph Goers commented on LOG4J2-1359:
-
I have modified the test that locates the caller class
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923236#comment-15923236
]
Ralph Goers commented on LOG4J2-1359:
-
https://bugs.openjdk.java.net/browse/JDK-8176593 has been
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907673#comment-15907673
]
Ralph Goers commented on LOG4J2-1359:
-
Yes, I posted to the open jdk list and referenced this Jira
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906837#comment-15906837
]
Ralph Goers edited comment on LOG4J2-1359 at 3/13/17 5:22 AM:
--
I have copied
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906837#comment-15906837
]
Ralph Goers edited comment on LOG4J2-1359 at 3/13/17 5:21 AM:
--
I have copied
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906837#comment-15906837
]
Ralph Goers edited comment on LOG4J2-1359 at 3/13/17 5:12 AM:
--
I have copied
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906837#comment-15906837
]
Ralph Goers edited comment on LOG4J2-1359 at 3/13/17 5:10 AM:
--
I have copied
18:31, Matt Sicker <boa...@gmail.com
> <mailto:boa...@gmail.com>> wrote:
> Created a request, not sure if it's public:
> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-13651
> <https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906837#comment-15906837
]
Ralph Goers commented on LOG4J2-1359:
-
I have copied the benchmarks from the sitepoint article
but keep the user lists as
> is. Shall we move forward with combining them now?
>
> On 10 March 2017 at 12:27, Dominik Psenner <dpsen...@gmail.com
> <mailto:dpsen...@gmail.com>> wrote:
> Total agreement.
>
> On 10 Mar 2017 6:26 p.m., "Ralph Goers" <
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906252#comment-15906252
]
Ralph Goers commented on LOG4J2-1359:
-
Let's see if I can help. First, I suggest you read
https
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906196#comment-15906196
]
Ralph Goers edited comment on LOG4J2-1359 at 3/11/17 12:59 PM:
---
I need
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906196#comment-15906196
]
Ralph Goers commented on LOG4J2-1359:
-
I need to get back to this...
Java 9 provides multi-version
doesn't cause
>>> any issues currently. The main idea here is whether we should merge the dev
>>> lists into one, or if we need a common dev list for all devs to subscribe
>>> to (general@ doesn't sound appropriate, but I don't know what that list is
>>&
> On 9 March 2017 at 10:26, Ralph Goers <ralph.go...@dslextreme.com
> <mailto:ralph.go...@dslextreme.com>> wrote:
> You should note that while we consider all votes only PMC votes are
> “binding”. I don’t think that changes much however.
>
> From a PMC perspective I ha
vote:
>
> log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ ->
> d...@logging.apache.org <mailto:d...@logging.apache.org>
> Matt Sicker: +1
> Ralph Goers: +1
> Stefan Bodewig: +1
> Sven Rautenverg: -1
> Thorsten Schöning: -0
> Ivan Habunek: -0
> Dominik Psenn
017, at 8:59 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote:
>
> I am a bit lost here.
>
> On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal <mikael.stal...@magine.com
> <mailto:mikael.stal...@magine.com>> wrote:
> Change to what?
>
> On Thu,
The instructions for what will be in the zip and tar balls will have to change.
Ralph
> On Mar 9, 2017, at 8:01 AM, Matt Sicker wrote:
>
> If you have time before the weekend, you could try copying over the
> log4j-distribution section from the main pom files. The "release"
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903224#comment-15903224
]
Ralph Goers commented on LOG4J2-1841:
-
Yes, this sounds pretty serous to me too.
> Probl
+1
Note that generally a -1 is a veto only on code commits. On everything else it
just means you are against the proposal. However, we generally strive for
consensus so great weight is given to binding votes that are opposed.
Ralph
> On Mar 7, 2017, at 9:23 PM, Matt Sicker
ilto:mikael.stal...@magine.com>> wrote:
>>
>>> I would like to keep package and artifact names, and bump version to 11.0.
>>>
>>> On Mar 1, 2017 4:04 PM, "Matt Sicker" <boa...@gmail.com
>>> <mailto:boa...@gmail.com>> wrot
ll try to do this in the next month.
>
> Remko
>
> Sent from my iPhone
>
>> On Mar 3, 2017, at 17:24, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>>
>> Remko,
>>
>> Would it be possible for you to update the performance page for the next
>
[
https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-1836.
---
> API Version is incorrect
>
>
> Key:
[
https://issues.apache.org/jira/browse/LOG4J2-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1836.
-
Resolution: Fixed
Fix Version/s: 2.8.2
> API Version is incorr
I created LOG4J2-1836 to address this.
Ralph
> On Mar 3, 2017, at 12:01 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> Likewise, I suspect that ProviderUtil should only list 2.6.0 as a compatible
> version since the implementation must be at that level or
Ralph Goers created LOG4J2-1836:
---
Summary: API Version is incorrect
Key: LOG4J2-1836
URL: https://issues.apache.org/jira/browse/LOG4J2-1836
Project: Log4j 2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4J2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1381:
Fix Version/s: (was: 2.8.1)
2.8.2
> Documentat
[
https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1229:
Fix Version/s: (was: 2.8.1)
2.8.2
> Error creating log
[
https://issues.apache.org/jira/browse/LOG4J2-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1498:
Fix Version/s: (was: 2.8.1)
2.8.2
> [Java 9] fix dependency on old
[
https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-915:
---
Fix Version/s: (was: 2.8.1)
2.8.2
> Wrong timestamp of filename w
[
https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1576:
Fix Version/s: (was: 2.8.1)
2.8.2
> Better automated backwa
[
https://issues.apache.org/jira/browse/LOG4J2-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1341:
Fix Version/s: (was: 2.8.1)
2.8.2
> (GC) Avoid allocating temporary obje
[
https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1812:
Fix Version/s: (was: 2.8.1)
2.8.2
> Improve error message when log4
[
https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1086:
Fix Version/s: (was: 2.8.1)
2.8.2
> SizeBasedTriggeringPol
[
https://issues.apache.org/jira/browse/LOG4J2-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1477:
Fix Version/s: (was: 2.8.1)
2.8.2
> @NonNull support (for @NonNullByDefa
[
https://issues.apache.org/jira/browse/LOG4J2-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1246:
Fix Version/s: (was: 2.8.1)
2.8.2
> PatternLayout %date conversion patt
[
https://issues.apache.org/jira/browse/LOG4J2-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1261:
Fix Version/s: (was: 2.8.1)
2.8.2
> Replace usage of deprecated L
[
https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1395:
Fix Version/s: (was: 2.8.1)
2.8.2
> Add "direct" option to Co
[
https://issues.apache.org/jira/browse/LOG4J2-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1410:
Fix Version/s: (was: 2.8.1)
2.8.2
> Add new LiteTimeoutBlockingWaitStrat
[
https://issues.apache.org/jira/browse/LOG4J2-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1603:
Fix Version/s: (was: 2.8.1)
2.8.2
> Redo hashCode() and equals() meth
[
https://issues.apache.org/jira/browse/LOG4J2-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1521:
Fix Version/s: (was: 2.8.1)
2.8.2
> StringIndexOutOfBoundsException thr
[
https://issues.apache.org/jira/browse/LOG4J2-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1760:
Fix Version/s: (was: 2.8.1)
2.8.2
> AsyncAppen
[
https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1013:
Fix Version/s: (was: 2.8.1)
2.8.2
> Log4j2 Main Arguments Lookup by n
1 - 100 of 4478 matches
Mail list logo