Le jeudi 20 février 2020, 13:53:29 CET EDMONDO SENA a écrit :
> Hi All,
>
> Please, Please:
>
> Is Syslog4j compatible with Log4j 2?
> I've the following jars:
>
> - Syslog4j-09.46-bin.jar and
> - syslog4j-0.9.57.jar
>
> but it seems that doesn't supporting Log4j 2.
> Can you help me?
Apache Ma
I think this is not possible for security reasons, you cannot trust pull
requests to have malicious code. The Jenkins builds are not that isolated.
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Elliotte Rusty Harold
Gesendet: Thursday, February 20, 2020 1:46:5
Anything that goes to Central is immutable .. so no edits or updates or
whatever. Make sure you keep that in mind
Manfred
Jonathan Valliere wrote on 2020-02-20 09:50 (GMT -08:00):
> Just indicate a date in the pom at which point the relocation warning turns
> into a relocation error. date. S
Just indicate a date in the pom at which point the relocation warning turns
into a relocation error. date. So you warn for a year then you
keep it up on central for an additional year in which it throws errors but
indicates to the redirection information.
On Thu, Feb 20, 2020 at 2:55 AM Hervé BOUT
Hi All,
Please, Please:
Is Syslog4j compatible with Log4j 2?
I've the following jars:
- Syslog4j-09.46-bin.jar and
- syslog4j-0.9.57.jar
but it seems that doesn't supporting Log4j 2.
Can you help me?
-
To unsubscribe, e-mai
Elliotte,
the problem is that the branch tested on ASF Jenkins has not relation
with the PR.
Jenkins has automatic binding but only if the build is triggered by
github, in that case github sends some kind of handle to the PR
Enrico
Il giorno gio 20 feb 2020 alle ore 13:47 Elliotte Rusty Harold
h
Is it possible to integrate the Jenkins builds with Github as Traivs
and CircleCI do? That is, to have Jenkins report build status on a PR
back to Github as a hook?
--
Elliotte Rusty Harold
elh...@ibiblio.org
-
To unsubscribe, e
Hmm, tried again and was able to reproduce in my client but not in a
new client on the same laptop. So probably something wonky in that
particular checkout, though how it would produce that failure I don't
know.
OTOH now I see this error in the new and old client:
[INFO]
[INFO] --- maven-enforcer
Hi,
Is syslog4j compatible with Log4j 2?
Kind regards.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
