And there was a typo: log4j-streams should have been log4j-iostreams.
On 6 October 2014 18:05, Matt Sicker wrote:
> Figured out how to fix log4j-bom.
>
> On 6 October 2014 17:49, Matt Sicker wrote:
>
>> It appears that maven-release-plugin is not updating the log4j-iostreams
>> version in the l
Figured out how to fix log4j-bom.
On 6 October 2014 17:49, Matt Sicker wrote:
> It appears that maven-release-plugin is not updating the log4j-iostreams
> version in the log4j-bom module. Plus, we forgot to add log4j-jul to the
> bom. Chances are that log4j-jul wouldn't get a version update eith
FYI, I filed https://issues.apache.org/jira/browse/INFRA-8439 -
Logging Services Chainsaw code signing support
Scott
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: log4j-dev-h.
It appears that maven-release-plugin is not updating the log4j-iostreams
version in the log4j-bom module. Plus, we forgot to add log4j-jul to the
bom. Chances are that log4j-jul wouldn't get a version update either.
Thus, the log4j-2.1-rc4 tag is another dud. I can't figure this out. I
think Ralph
I looked at the commit emails for the recent changes but nothing caught my eye;
i'm fine with releasing what we have now.
FYI, I started a number of online courses and may have very little time to work
on log4j for the next month or two.
Regards, -Remko
Sent from my iPhone
> On 2014/10/07,
Alright I'm gonna check those colors out and choose one. Then I can start
RC4.
On 5 October 2014 00:27, Gary Gregory wrote:
> Maybe 152B55 or 061739
>
> See http://paletton.com/#uid=13J0u0kaFw0g0qFqFg0w0aF
>
> Gary
>
> On Sat, Oct 4, 2014 at 11:37 PM, Matt Sicker wrote:
>
>> You got a hex c
Not here.
Gary
On Mon, Oct 6, 2014 at 3:19 PM, Matt Sicker wrote:
> That's what I mean. Any more polishing? Any APIs you forgot to fix before
> 2.1 that can be done in a couple hours or so? That sort of thing.
>
> On 6 October 2014 13:11, Gary Gregory wrote:
>
>> I do not think we should add _
That's what I mean. Any more polishing? Any APIs you forgot to fix before
2.1 that can be done in a couple hours or so? That sort of thing.
On 6 October 2014 13:11, Gary Gregory wrote:
> I do not think we should add _anything_ for 2.1. If I have an itch before
> 2.1 I'll create a branch. Ideally
I do not think we should add _anything_ for 2.1. If I have an itch before
2.1 I'll create a branch. Ideally, our time should be spent polishing.
Gary
On Mon, Oct 6, 2014 at 2:02 PM, Matt Sicker wrote:
> I should have time to start the release again (most likely tonight), but
> if there's anythi
I should have time to start the release again (most likely tonight), but if
there's anything else we want to get in for 2.1, then I may have to step
down.
On 6 October 2014 12:49, Ralph Goers wrote:
> If Matt is not available I will have the time this week to do a release.
>
> Ralph
>
> On Oct 6
If Matt is not available I will have the time this week to do a release.
Ralph
On Oct 6, 2014, at 10:03 AM, Gary Gregory wrote:
> Thanks to Matt's RM and coding efforts over the weekend, we went through
> three RCs and found and resolved a slew of issues.
>
> Thanks Matt once again.
>
> It l
Thanks to Matt's RM and coding efforts over the weekend, we went through
three RCs and found and resolved a slew of issues.
Thanks Matt once again.
It looks like Matt added the shutdown hook he had discussed and other OSGi
related changes. My Apache time is quite limited this week so if anyone
el
[
https://issues.apache.org/jira/browse/LOG4J2-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudhakar updated LOG4J2-870:
Attachment: log4j4.png
log4j3.png
log4j2.png
> log4j2 with servlet 3.0 conta
[
https://issues.apache.org/jira/browse/LOG4J2-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudhakar updated LOG4J2-870:
Attachment: log4j1.png
> log4j2 with servlet 3.0 container in WAS8.5 not working
> -
Sudhakar created LOG4J2-870:
---
Summary: log4j2 with servlet 3.0 container in WAS8.5 not working
Key: LOG4J2-870
URL: https://issues.apache.org/jira/browse/LOG4J2-870
Project: Log4j 2
Issue Type: Que
Lucas Pouzac created LOG4J2-869:
---
Summary: Monitor contention at
org.apache.logging.log4j.core.util.Loader.*
Key: LOG4J2-869
URL: https://issues.apache.org/jira/browse/LOG4J2-869
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Pouzac updated LOG4J2-869:
Attachment: monitor_contention_log4j.png
> Monitor contention at org.apache.logging.log4j.core.util.
[
https://issues.apache.org/jira/browse/LOG4J2-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrille Karmann closed LOG4J2-729.
--
Verified, thanks. Closing now.
> Emit warning message to console if no config file found
>
When I run mvn test in log4j-1.2-api (on current master in git), it worked
fine
On Ubuntu 14.04, Maven 3.0.5, Oracle Java 1.8.0_20, Linux 3.13.0-36-generic
(I run Linux as host OS, without virtualization.)
On Sat, Oct 4, 2014 at 2:10 PM, Gary Gregory wrote:
> Odd:
>
> I see a test failure only
19 matches
Mail list logo
