[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978166#comment-15978166
]
Ralph Goers commented on LOG4J2-1359:
-
This has now been pushed to master.
> Add sup
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1359.
-
Resolution: Fixed
Please verify and close.
> Add support for Java 9 StackWalker API in Reflectio
I’ve pushed the support for Java 9 and Stackwalker. Java 9 is now required to
build Log4j in addition to Java 7.
Ralph
Good Morning Chen
Sad to see you leave. You can unsubscribe yourself by sending a mail to
dev-unsubscr...@logging.apache.org.
Cheers,
Dominik
On 2017-04-21 03:52, Chen Y wrote:
Please remove me from this mailing list.
Thank you
On Apr 20, 2017 9:28 AM, "Mikael Ståldal" wrote:
https://w
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978162#comment-15978162
]
ASF subversion and git services commented on LOG4J2-1359:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978163#comment-15978163
]
ASF subversion and git services commented on LOG4J2-1359:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978161#comment-15978161
]
ASF subversion and git services commented on LOG4J2-1359:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978159#comment-15978159
]
ASF subversion and git services commented on LOG4J2-1359:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978160#comment-15978160
]
ASF subversion and git services commented on LOG4J2-1359:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978135#comment-15978135
]
ASF subversion and git services commented on LOG4J2-1858:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978133#comment-15978133
]
ASF subversion and git services commented on LOG4J2-1858:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978136#comment-15978136
]
ASF subversion and git services commented on LOG4J2-1858:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978137#comment-15978137
]
ASF subversion and git services commented on LOG4J2-1877:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978134#comment-15978134
]
ASF subversion and git services commented on LOG4J2-1858:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978132#comment-15978132
]
ASF subversion and git services commented on LOG4J2-1858:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978138#comment-15978138
]
ASF subversion and git services commented on LOG4J2-1807:
-
Commit
Potentially - it was quite finicky to get running. Depending on how
much access there is, it may not be feasible, as there are other
dependencies needed to build. From master, you need not only all of
the autotools, but also APR in order to compile. It should be
possible to simply build APR in t
Please remove me from this mailing list.
Thank you
On Apr 20, 2017 9:28 AM, "Mikael Ståldal" wrote:
> https://www.reddit.com/r/programming/comments/66ftqf/
> logging_levels_the_wrong_abstraction/
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikae
Can we get that Jenkins job set up on builds.a.o?
On 20 April 2017 at 19:48, Robert Middleton wrote:
> A few months ago, I took a look at the release for log4cxx and tried
> to get it to work properly; I didn't have much luck at the time, but
> I've taken another look at it recently and I think
A few months ago, I took a look at the release for log4cxx and tried
to get it to work properly; I didn't have much luck at the time, but
I've taken another look at it recently and I think that I have got it
working.
It's rather ugly, since the POM at this point is only used to call out
to autotoo
For instance, suppose I want to drop the level of all log messages in the
parent logger "org.example.project" by one priority except for error. So
this would map WARN -> INFO, INFO -> DEBUG, etc. I'm not exactly sure on a
DSL here, but it's more of a thought than a feature request right now.
On 20
I’d have to see an example to understand the benefit. As it is right now you
have to configure a logger for each thing you want to manage at its own logging
level. If you were going to “re-write” the logging level how would you do that
without having to configure each logger with the new level?
The conversations there make me think that some sort of ability to rewrite
log levels emitted from various loggers at configuration time could be
useful. For instance, some libraries are rather spammy in the info or warn
level, and having to suppress all non-error messages from those frameworks
doe
Sounds good and I *really* like the auto tagging of PR/s with Jira.
Not sure how ASF works, at least I haven’t been any real contributor to any
Apache projects _yet_.
log4j2 seemed to be a good start!
thanks,
Chandra
On 21 Apr 2017, 12:14 AM +0530, Matt Sicker , wrote:
> We have it set up as a
We have it set up as a convenience for PRs, though in theory we could make
Jenkins do it instead. The ASF has a policy of using our own resources for
most things, so I don't think we can even use Travis as our primary CI
anyways.
As for the Scala module there, we're almost ready to migrate them in
lol, I digged in a little bit, seems to be the issue of OOM.
[INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. FAILURE [ 29.531 s]
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (default-jar) on project
log4j-api-scala_2.11: Error assembling JA
That was a Travis build failure, right? That system is even less reliable
than our normal Jenkins system.
On Wed, Apr 19, 2017 at 20:01, Chandra
wrote:
> Yeah. I believe you. was just wondering why the all build failures. ;)
>
> thanks,
> Chandra
>
> On 20 Apr 2017, 5:33 AM +0530, Matt Sicker ,
Oh right, that's a difference. Anyways, if this isn't working with SBT, how
does it work properly with older versions?
On Thu, Apr 20, 2017 at 02:38, Mikael Ståldal
wrote:
> You need to build it with Java 8.
>
> On Thu, Apr 20, 2017 at 2:15 AM, Matt Sicker wrote:
>
> > It's the same maven build
Interesting comments. In the typical reddit fashion, I propose a Buzzfeed
listicle on logging based on the thread. Or at least some manual
enhancements.
On Thu, Apr 20, 2017 at 06:28, Mikael Ståldal
wrote:
>
> https://www.reddit.com/r/programming/comments/66ftqf/logging_levels_the_wrong_abstract
https://www.reddit.com/r/programming/comments/66ftqf/logging_levels_the_wrong_abstraction/
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.stal...@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Infor
[
https://issues.apache.org/jira/browse/LOG4J2-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976650#comment-15976650
]
Heiko Tappe commented on LOG4J2-1031:
-
I am curious: What exactly was less than satis
[
https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976645#comment-15976645
]
Anthony Maire commented on LOG4J2-1883:
---
Concerning the java.time.Instant allocatio
You need to build it with Java 8.
On Thu, Apr 20, 2017 at 2:15 AM, Matt Sicker wrote:
> It's the same maven build as log4j. Copying over the BUILDING.txt file
> would be a good idea, though.
>
> On 19 April 2017 at 11:52, Gary Gregory wrote:
>
> > Adding a BUILDING.txt to the root of the src zi
On 2017-04-19, Dominik Psenner wrote:
> I completely purged that mess from my memory. We need a solution that
> just works and links to generated code are not "the solution"©. :-)
> When I build log4net I get the following files:
> * log4net.dll
> * log4net.pdb
> * log4net.xml
> The latter is a
Hallo Thorsten
On 2017-04-19, Thorsten Schöning wrote:
> am Mittwoch, 19. April 2017 um 10:13 schrieben Sie:
>> As log4net uses maven to build the site as well, this could probably
>> solved by using the same skin (I've never tried to fiddle with that,
>> though).
> As log4cxx has done the same
35 matches
Mail list logo
