[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025440#comment-16025440
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user PascalSchumacher commented o
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:
1.228
Hi
I've pushed half of the old pull requests. It would be great if we could
have some discussion on those patches. The following pull requests are
still on my todo list for checking. I'll only be able to look at them in
about 2 weeks from now.
* pr/29
* pr/32
* pr/40
* pr/43
* pr/45
Cheers
2017
While applying the pull requests I stumbled upon pr/22 which is based on
the branch log4net-1.2.x. That branch has a lot of modifications but I am
unsure whether or not those changes have been merged into trunk or if there
has been a release made from that source. Stefan, do you recall what
happene
On 25 May 2017 2:37 p.m., "Stefan Bodewig" wrote:
I've asked infra to remove the repo:
https://issues.apache.org/jira/browse/INFRA-14233
On 2017-05-25, Dominik Psenner wrote:
> I have cloned the repository from [1] and fetched also all open pull
> requests. Unfortunately it is not possible to a
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025300#comment-16025300
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user PascalSchumacher commented o
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
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025294#comment-16025294
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user mikaelstaldal commented on t
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/79
Now it fails with the socket option test that has been fixed. Have you
synced with upstream?
---
If your project is set up for it, you can reply to this email and have your
reply appear
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025252#comment-16025252
]
ASF GitHub Bot commented on LOG4J2-1901:
GitHub user PascalSchumacher opened a pu
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/PascalSchumacher
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025098#comment-16025098
]
Mikael Ståldal commented on LOG4J2-1901:
The Socket options tests are fixed. Now
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024925#comment-16024925
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user mikaelstaldal commented on t
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/77
This has been fixed in master branch already.
---
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 hav
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024877#comment-16024877
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user garydgregory commented on th
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/77
Wouldn't this best be fixed with a JUnit assume?
---
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 h
[
https://issues.apache.org/jira/browse/LOG4J2-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajitha closed LOG4J2-1920.
--
Thanks for the excellent and prompt support. It worked like a charm. I am able
to use log4j in Android now.
> Sc
[
https://issues.apache.org/jira/browse/LOG4J2-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024769#comment-16024769
]
Ralph Goers commented on LOG4J2-1920:
-
I have deployed SNAPSHOTs to repository.apache
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024716#comment-16024716
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user PascalSchumacher closed the
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 th
I've asked infra to remove the repo:
https://issues.apache.org/jira/browse/INFRA-14233
On 2017-05-25, Dominik Psenner wrote:
> I have cloned the repository from [1] and fetched also all open pull
> requests. Unfortunately it is not possible to apply or fetch the pull
> requests into the new git r
21 matches
Mail list logo