[GitHub] logging-log4j2 issue #102: Try to fix build on travis

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/102 Now the log4j-server jar just needs to be build and published to the apache snapshot repository. --- If your project is set up for it, you can reply to this email and have your

[GitHub] logging-log4j-tools issue #1: create test-jar, which is used by the log4j-co...

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j-tools/pull/1 Adding the configuration to the parent pom cause the build to fail: ``` [INFO] --- maven-jar-plugin:3.0.0:test-jar (default) @ log4j-tools --- [WARNING] JAR will

[GitHub] logging-log4j-tools pull request #1: create test-jar, which is used by the l...

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/logging-log4j-tools/pull/1 create test-jar, which is used by the log4j-core-its module required to fix log4j2 build on travis (see https://github.com/apache/logging-log4j2/pull/102) You can merge this

[GitHub] logging-log4j2 issue #102: replace oraclejdk7 with openjdk7 on travis

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/102 log4j-core-its fail to build because: >logging.log4j:log4j-core-its:jar:2.9-SNAPSHOT: Could not find artifact org.apache.logging.log4j:log4j-server:jar:tests:2.9-SNAPSHOT

[GitHub] logging-log4j2 pull request #102: replace oraclejdk7 with openjdk7 on travis

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/logging-log4j2/pull/102 replace oraclejdk7 with openjdk7 on travis I'm giving it another try (now that the scala api stuff was moved). You can merge this pull request into a Git repository by ru

[GitHub] logging-log4j2 issue #79: LOG4J2-1901: Fix travis-ci build

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/79 Added assumes to skip these tests on travis-ci. Now a test of og4j-api-scala_2.11 fails: [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed

[GitHub] logging-log4j2 issue #79: LOG4J2-1901: Fix travis-ci build

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/79 Yes. The problem is that these tests also fail on java 7 when run on travis. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] logging-log4j2 pull request #79: LOG4J2-1901: Fix travis-ci build

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/logging-log4j2/pull/79 LOG4J2-1901: Fix travis-ci build remove apt-get, use trusty dist You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] logging-log4j2 pull request #77: LOG4J2-1901 - Fix travis-ci build

Github user PascalSchumacher closed the pull request at: https://github.com/apache/logging-log4j2/pull/77 --- 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

[GitHub] logging-log4j2 pull request #77: LOG4J2-1901 - Fix travis-ci build

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/logging-log4j2/pull/77 LOG4J2-1901 - Fix travis-ci build temporary comment out failing asserts to see if build passes Just a test, not ready to merge! You can merge this pull request into a Git

[GitHub] logging-log4j2 pull request #76: try to fix build on travis

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/logging-log4j2/pull/76 try to fix build on travis You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/logging-log4j2 try_to_fix_travis

[GitHub] logging-log4j2 issue #75: trim levels read from properties file to remove tr...

Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/75 I guess there should be a jira issue for this, so I created https://issues.apache.org/jira/browse/LOG4J2-1890 --- If your project is set up for it, you can reply to this email and