Jenkins build is back to stable : Log4j 2.x #2863

See

Re: [Log4j] release 2.9

It should be possible. We need to take a hard look at the bugs that have been reported. Some seem pretty important. Ralph > On Jul 4, 2017, at 2:00 PM, Gary Gregory wrote: > > Hi All, > > I would live to see our 2.9 at the end of July at the latest. Big deadline > for me. Is that a possibili

[jira] [Commented] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074111#comment-16074111 ] Remko Popma commented on LOG4J2-1967: - Question: Does system property {{logfile}} hav

Jenkins build is unstable: Log4j 2.x #2862

See

[Log4j] release 2.9

Hi All, I would live to see our 2.9 at the end of July at the latest. Big deadline for me. Is that a possibility? Gary

[jira] [Created] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

Paul K created LOG4J2-1967: -- Summary: Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile Key: LOG4J2-1967 URL: https://issues.apache.org/jir

Build failed in Jenkins: Log4j 2.x #2861

See Changes: [ggregory] Javadoc tweak. -- [...truncated 1.25 MB...] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #44

Hi, it seems I can't get this to be working. The problems are mainly two: 1. nant runs nunit and outputs the xml in nunit format which jenkins can't parse; it would be necessary to XSL transform the xml into junit format :-( 2. since tests fail, nant always exits with code 1 and I can't get jenki

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #44

See -- [...truncated 63.22 KB...] compile-net-4.5-current-configuration: check-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\lo

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #43

See -- [...truncated 63.22 KB...] compile-net-4.5-current-configuration: check-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\lo

[jira] [Resolved] (LOG4J2-1966) Include separator option of PatternLayout in manual (and other updates)

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1966. -- Resolution: Fixed Fix Version/s: 2.9 Please verify and close. To verify, you can clone

[jira] [Commented] (LOG4J2-1966) Include separator option of PatternLayout in manual (and other updates)

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073939#comment-16073939 ] ASF subversion and git services commented on LOG4J2-1966: - Commit

[jira] [Updated] (LOG4J2-1966) Include separator option of PatternLayout in manual (and other updates)

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1966: - Summary: Include separator option of PatternLayout in manual (and other updates) (was: Include s

[jira] [Assigned] (LOG4J2-1966) Include separator option of PatternLayout in manual

[ https://issues.apache.org/jira/browse/LOG4J2-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-1966: Assignee: Gary Gregory > Include separator option of PatternLayout in manual > ---

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #41

See -- [...truncated 9.34 KB...] check-build-debug: check-build-defines: set-net-3.5-runtime-configuration: check-log4net-basedir: check-current-bin-di

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #40

See -- [...truncated 9.29 KB...] check-sdkdoc-dir: check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-net-3.5-

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #39

See -- [...truncated 63.22 KB...] compile-net-4.5-current-configuration: check-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\lo

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #38

See -- [...truncated 9.37 KB...] check-build-debug: check-build-defines: set-net-3.5-runtime-configuration: check-log4net-basedir: check-current-bin-dir

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #37

See -- [...truncated 63.31 KB...] check-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCPODUF6LCE

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #36

See -- [...truncated 63.23 KB...] compile-net-4.5-current-configuration: check-bin-dir: [mkdir] Creating directory 'f:\jenkins\jenkins-slave\workspace\lo

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #35

See -- [...truncated 50.58 KB...] set-build-configuration-flags: compile-net-4.0-cp-current-configuration: check-bin-dir: check-doc-dir: check-sdkdoc-d

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #34

See -- [...truncated 112.19 KB...] [csc] f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCPODUF6LCE45226EBUR4GNVLYPMYVC23Z4ITBOMNJT3CA2

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #33

See -- [...truncated 126.03 KB...] [csc] f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCPODUF6LCE45226EBUR4GNVLYPMYVC23Z4ITBOMNJT3CA2

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #32

See -- [...truncated 24.30 KB...] compile-net-3.5-cp: set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile-

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #31

See -- [...truncated 22.32 KB...] compile-net-3.5-cp: set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile-

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #30

See -- [...truncated 10.49 KB...] check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-net-3.5-runtime-configurat

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #29

See -- [...truncated 22.11 KB...] compile-net-3.5-cp: set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile-n

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073317#comment-16073317 ] Roman Sosnin commented on LOG4J2-1933: -- Opened PR in Github: https://github.com/apac

[GitHub] logging-log4j2 pull request #91: failing test - irregular log4j2.json nodes ...

GitHub user romanso123 opened a pull request: https://github.com/apache/logging-log4j2/pull/91 failing test - irregular log4j2.json nodes order Failing test, showing that log4j2.json config file nodes specific order can fail log4j2 framework functionality. Test description:

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #27

See -- [...truncated 21.99 KB...] compile-net-3.5-cp: set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #26

See -- [...truncated 111.29 KB...] [csc] f:\jenkins\jenkins-slave\workspace\log4net_feature_cd-pipeline-76KUCPODUF6LCE45226EBUR4GNVLYPMYVC23Z4ITBOMNJT3CA2

Build failed in Jenkins: logging-log4net » feature/cd-pipeline #23

See -- [...truncated 105.63 KB...] [exec] [INFO] --- maven-site-plugin:3.4:site (default-cli) @ apache-log4net --- [exec] [INFO] configuring report pl