Please see my question:
https://issues.apache.org/jira/browse/LOG4J2-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551742#comment-16551742
Gary
What should we do here:
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @
log4j-flume-ng ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 11 source files to
C:\vcs\git\apache\logging\logging-log4j2\log4j-flume-ng\target\classes
Processing annotations
Annotati
What's up with these warnings:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for
org.apache.logging.log4j.samples:log4j-samples-flume-remote:war:3.0.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be uniq
> On Jul 21, 2018, at 8:24 AM, Dominik Psenner wrote:
>
> Jenkins slaves currently have very low disk space. This may be a out of
> disk space in disguise.
I definitely agree with that thought. Disk space issues cause all sorts of
weird exceptions in Jenkins because that’s its data storage m
Jenkins slaves currently have very low disk space. This may be a out of
disk space in disguise.
On Sat, 21 Jul 2018, 14:12 Rob Tompkins, wrote:
> Looks like Jenkins timed out on checkout or something.
>
> > On Jul 20, 2018, at 1:08 PM, Ralph Goers
> wrote:
> >
> > No idea.
> >
> > Ralph
> >
> >
Looks like Jenkins timed out on checkout or something.
> On Jul 20, 2018, at 1:08 PM, Ralph Goers wrote:
>
> No idea.
>
> Ralph
>
>> On Jul 20, 2018, at 9:56 AM, Gary Gregory wrote:
>>
>> Could this be a corrupt local repo or an out of disk space issue?
>>
>> Gary
>>
>> On Fri, Jul 20, 20