[
https://issues.apache.org/jira/browse/LOG4J2-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1938.
Resolution: Fixed
Closing. See previous comment for commit info.
> Update Jackson from 2.8.7 to 2.
[
https://issues.apache.org/jira/browse/LOG4J2-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047324#comment-16047324
]
ASF subversion and git services commented on LOG4J2-1938:
-
Commit
Gary Gregory created LOG4J2-1938:
Summary: Update Jackson from 2.8.7 to 2.8.9
Key: LOG4J2-1938
URL: https://issues.apache.org/jira/browse/LOG4J2-1938
Project: Log4j 2
Issue Type: Task
Hi Ralph,
would you please grant me karma to add/modify log4net build configurations
on jenkins?
Warm regards
--
Dominik Psenner
Yep, sorry about that!
Gary
On Mon, Jun 12, 2017 at 2:10 PM, Ralph Goers
wrote:
> Wrong list?
>
> Ralph
>
> > On Jun 12, 2017, at 1:46 PM, Gary Gregory
> wrote:
> >
> > Hi Rob,
> >
> > Thank you for pushing this through.
> >
> > Would you consider doing the same for the few other Travis builds
Wrong list?
Ralph
> On Jun 12, 2017, at 1:46 PM, Gary Gregory wrote:
>
> Hi Rob,
>
> Thank you for pushing this through.
>
> Would you consider doing the same for the few other Travis builds we have
> in Commons?
>
> Thank you,
> Gary
>
> -- Forwarded message --
> From:
> D
Hi Rob,
Thank you for pushing this through.
Would you consider doing the same for the few other Travis builds we have
in Commons?
Thank you,
Gary
-- Forwarded message --
From:
Date: Mon, Jun 12, 2017 at 4:58 AM
Subject: [6/6] [text] Merge branch 'travis-ibmjdk8' of
https://gith
In theory, you can use Jenkins pipelines scripts in your projects, but I
haven't tested that out yet. It's the system we're using at my work.
On 12 June 2017 at 14:25, Dominik Psenner wrote:
> I envision to automate the build and publishing process. At work we are
> migrating to git and along wi
I envision to automate the build and publishing process. At work we are
migrating to git and along with that we are going to set up our (insane)
build process with gitlab runners executed by virtualbox executors. See
https://docs.gitlab.com/runner/ and
https://docs.gitlab.com/ee/ci/yaml/README.html
We're doing the same in log4j right now as well. I'd love to figure out a
more fluid way of doing this eventually.
On 12 June 2017 at 10:16, Stefan Bodewig wrote:
> On 2017-06-12, Matt Sicker wrote:
>
> > That's an interesting use case. Are you using gitpubsub instead of
> > svnpubsub for the si
[
https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046716#comment-16046716
]
Helber Belmiro commented on LOG4J2-1936:
[~jvz] The error occurs only in async mo
[
https://issues.apache.org/jira/browse/LOG4J2-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Dumont updated LOG4J2-1937:
-
Environment:
Java 1.8.0_131
was:
MacOSX El Capitan, Java 1.8.0_131
> Including log
[
https://issues.apache.org/jira/browse/LOG4J2-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Dumont updated LOG4J2-1937:
-
Environment:
MacOSX El Capitan, Java 1.8.0_131
was:
MacOSX El Capitan
{code}
$> java
[
https://issues.apache.org/jira/browse/LOG4J2-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Dumont updated LOG4J2-1937:
-
Attachment: TestProject.zip
I've added a project with the minimum code to reproduce the i
Guillaume Dumont created LOG4J2-1937:
Summary: Including log4j-core yields a compilation warning with
-Xlint:all
Key: LOG4J2-1937
URL: https://issues.apache.org/jira/browse/LOG4J2-1937
Project: Lo
On 2017-06-12, Matt Sicker wrote:
> That's an interesting use case. Are you using gitpubsub instead of
> svnpubsub for the site then?
"mvn site" plus manual copy over to svn plus the logging site's
svnpubsub. Yes, it is painful :-)
Stefan
[
https://issues.apache.org/jira/browse/LOG4J2-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046654#comment-16046654
]
Matt Sicker commented on LOG4J2-1936:
-
Do you get a similar error when using the norm
That's an interesting use case. Are you using gitpubsub instead of
svnpubsub for the site then?
On 10 June 2017 at 12:41, Dominik Psenner wrote:
> We have also the site versioned in the same repository. Updates to the
> website do not necessarily synchronize well with the library releases. So
>
Helber Belmiro created LOG4J2-1936:
--
Summary: ClassNotFoundException when making all loggers
asynchronous under OSGi environment
Key: LOG4J2-1936
URL: https://issues.apache.org/jira/browse/LOG4J2-1936
Hi,
While implementing an *org.apache.logging.log4j.core.Appender*, the only
*append()* method that needs to be implemented takes a single *LogEvent*
argument: *void append(LogEvent event)*. This makes it impossible to handle
and resolve batch append operations at the appender level. This results
20 matches
Mail list logo
