[
https://issues.apache.org/jira/browse/LOG4J2-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114019#comment-16114019
]
Kohei Tamura commented on LOG4J2-1922:
--
TcpSocketServer couldn't be started with _-p
Github user kpm1985 closed the pull request at:
https://github.com/apache/logging-log4j2/pull/104
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featur
Github user kpm1985 commented on the issue:
https://github.com/apache/logging-log4j2/pull/104
I will create a new patch and pull request that addresses the minimal set
of changes to close LOG4J2-1997. Although the changes are fairly trivial, I
realize that 27 files might be too large.
[
https://issues.apache.org/jira/browse/LOG4J2-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113905#comment-16113905
]
Paul Burrowes commented on LOG4J2-922:
--
This should be reopened and fixed. The commit
Paul Burrowes created LOG4J2-2003:
-
Summary: Hierarchical component properties
Key: LOG4J2-2003
URL: https://issues.apache.org/jira/browse/LOG4J2-2003
Project: Log4j 2
Issue Type: Wish
Paul Burrowes created LOG4J2-2002:
-
Summary: DefaultConfigurationBuilder.writeXmlAttributes does not
handle null attribute values
Key: LOG4J2-2002
URL: https://issues.apache.org/jira/browse/LOG4J2-2002
Could either a new component or new project be created in JIRA as
well? This was discussed a few months ago but as far as I am aware
nothing ever happened.
-Robert Middleton
On Thu, Aug 3, 2017 at 2:32 PM, Matt Sicker wrote:
> For Chainsaw, we'd only need the one version. When we eventually get
[
https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113257#comment-16113257
]
Matt Sicker commented on LOG4J2-1949:
-
Default methods would have prevented several n
For Chainsaw, we'd only need the one version. When we eventually get Log4j2
into a pipeline, we'll need both Java 7 and 9, maybe even Java 8 for
testing purposes (plus Java 8 would be required for the Log4jScala build).
On 3 August 2017 at 02:16, Dominik Psenner wrote:
> The log4net jenkinsfile
[
https://issues.apache.org/jira/browse/LOG4J2-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113026#comment-16113026
]
Gary Gregory commented on LOG4J2-1922:
--
You can run it from the command line with {{
[
https://issues.apache.org/jira/browse/LOG4J2-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113007#comment-16113007
]
Gary Gregory commented on LOG4J2-2001:
--
Thank you for your report.
Please feel free
[
https://issues.apache.org/jira/browse/LOG4J2-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112997#comment-16112997
]
Gary Gregory commented on LOG4J2-1998:
--
There are no hard-coded levels in {{RegExFil
The error with the missing artifact happens when you skip tests. The test that
failed for you never fails for me on OS X but fails randomly in Jenkins. I’m
not sure why no one has looked at it yet.
Ralph
> On Aug 3, 2017, at 6:52 AM, Jörn Huxhorn wrote:
>
> OK, everything works for me with 2
OK, everything works for me with 2.9-SNAPSHOT.
I can receive JSON, YAML and XML events just fine.
I had the following error while building:
[ERROR] Failed to execute goal on project log4j-core-its: Could not resolve
dependencies for project
org.apache.logging.log4j:log4j-core-its:jar:2.9-SNAPSHO
[
https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112697#comment-16112697
]
Chris Slater edited comment on LOG4J2-1949 at 8/3/17 1:34 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112697#comment-16112697
]
Chris Slater commented on LOG4J2-1949:
--
I did not change the LifeCycle interfaces in
Yes, that test is known to be unstablle.
Just build with -DskipTests
On 2017-08-03 11:24, Jörn Huxhorn wrote:
I get test failures building against HEAD
(3ac727026f295941fe71a34d6c80afc242f38c0f).
Environment:
$ mvn -version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-
I get test failures building against HEAD
(3ac727026f295941fe71a34d6c80afc242f38c0f).
Environment:
$ mvn -version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T21:39:06+02:00)
Maven home: /Users/huxi/.sdkman/candidates/maven/current
Java version: 1.8.0_144, vendor: Ora
GitHub user fabriziocucci opened a pull request:
https://github.com/apache/logging-log4j2/pull/105
Modernized (Java 8 style) markers examples
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fabriziocucci/logging-log4j2 patch-1
A
The log4net jenkinsfile pipeline is complicated because it targets many
different frameworks, each one requiring different conditional compiletime
constants. This java application should be by far easier to build by
targeting the smallest java version to be supported.
I would certainly not expect
20 matches
Mail list logo
