Although a version number property could be used, too, with appropriately
simple build configuration instructions. I know Maven supports it for
import at least.
On 9 January 2017 at 21:47, Matt Sicker wrote:
> Ok, I think it would've been annoying to match the version numbers.
> However, each ve
Jira is down right now, but I have this RFC:
https://github.com/apache/logging-log4j-boot
On 8 January 2017 at 02:16, Remko Popma wrote:
> Speaking of slf4j, I would like to evangelize that applications should
> code to the Log4j2 API as a best practice. See also
> http://stackoverflow.com/a/415
I still like the work I did with executor services, so I'll leave it at
that ;-) Sure it turns out there is a bug on reconfigure but it's fixable
without throwing it all out. I'm swamped at work ATM so I cannot spend time
dealing with too much FOSS this week (as was last week). Good luck :-)
Gary
Jira is down today, so I'll respond here. The log4j-boot-logback module's
intention is to promote the use of log4j-api as a general logging facade
while providing a migration path for logback users. There is still
confusion in the community of whether or not log4j-api is a replacement for
slf4j-api
Some feedback:
1. Why remove Log4jThreadFactory.createThreadFactory?
CassandraRule was using it and now needs to use the constructor.
2. The ConfigurationScheduler may create a thread pool with size zero.
ConfigurationScheduler::incrementScheduledItems is only called if
monitorInterval is positive
Agreed. Plus, this could make it a bit easier to find for users and
contributors I think.
On 11 January 2017 at 15:46, Apache wrote:
> I think we should make a separate repo for log4j-samples. The build of
> this is not part of our release process so it really makes no sense, other
> than makin
This is a good migration path to allow for that. I'd still like to see
log4j-core trimmed down a bit, too.
On 11 January 2017 at 15:28, Mikael Ståldal
wrote:
> I think that we should still split up log4j-core though.
>
> On Jan 10, 2017 3:18 AM, "Matt Sicker" wrote:
>
>> Going to go with the na
Hello Everyone
This email is to tell you about ASF participation at FOSDEM. The event
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping
that many people from our ASF projects will be there.
https://fosdem.org/2017/
Attending FOSDEM is completely free and the ASF will ag
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820805#comment-15820805
]
Mikael Ståldal commented on LOG4J2-1748:
I have a solution for this and LOG4J-178
[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal resolved LOG4J2-1780.
Resolution: Fixed
Fix Version/s: 2.8
See branch LOG4J2-1748and1780-remove-ExecutorSe
[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1780:
---
Summary: Eliminate the use of the ExecutorServices in the LoggerContext
(was: LoggerContext
[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal reassigned LOG4J2-1780:
--
Assignee: Mikael Ståldal
> LoggerContext does not shut down old executor services when
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820759#comment-15820759
]
Mikael Ståldal commented on LOG4J2-1748:
I don't think it is that complicated to
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820692#comment-15820692
]
Remko Popma commented on LOG4J2-1748:
-
I disagree. We've seen problems in the past wh
Per our twitter status, and status.apache.org ... yeah, we're having
problems right now with Jira. The machine appears to have some hardware
faults, so we're looking at our options.
Cheers,
Greg Stein
Infrastructure Administrator, ASF
On Thu, Jan 12, 2017 at 3:58 AM, Remko Popma wrote:
>
> JIR
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820630#comment-15820630
]
Mikael Ståldal commented on LOG4J2-1748:
The root cause of the problem is using n
> JIRA problem:
>
> Opening https://issues.apache.org/jira/browse/LOG4J2
>
> redirects to
> https://issues.apache.org/jira/browse/LOG4J2/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
>
> Which shows
> Issues
> Tab panel 'com.atlassian.jira.jira-projects-plugin:issues-panel
JIRA problem:
Opening https://issues.apache.org/jira/browse/LOG4J2
redirects to
https://issues.apache.org/jira/browse/LOG4J2/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
Which shows
Issues
Tab panel 'com.atlassian.jira.jira-projects-plugin:issues-panel' failed to
render.
[
https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820604#comment-15820604
]
Mikael Ståldal commented on LOG4J2-1748:
Yes, I agree.
But while waiting for us
19 matches
Mail list logo
