I’ve turned my attention to Log4j Audit and hope to finish that up before
returning to work next week. I will be taking vacation for a week starting next
weekend and don’t plan on doing any releases at that time.
Ralph
> On Dec 30, 2017, at 12:29 PM, Gary Gregory wrote:
>
> Hi All,
>
> And
Hi All,
And almost happy New Year.
How do we look for a release?
Gary
Yes, it does.
On 2017-12-23 17:39, Ralph Goers wrote:
I am using the same version of Maven and Java. Does your reactor order match
mine?
I am using the same version of Maven and Java. Does your reactor order match
mine?
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 . SUCCESS [ 1.532 s]
[INFO] Apache Log4j API Java 9 support SUCCESS [ 4.568 s]
[INFO] Apache Log4j AP
Did not help for me.
On 2017-12-23 06:46, Matt Sicker wrote:
That OSGi test failure looks like one that could maybe be solved by doing a
"mvn install -DskipTests" first as it's trying to find a snapshot jar.
I just tried with latest master. No errors in log4j-api, but in log4j-osgi:
$ mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: /opt/apache-maven-3.3.9
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: /opt/jvm/jdk1.8.0_144
That OSGi test failure looks like one that could maybe be solved by doing a
"mvn install -DskipTests" first as it's trying to find a snapshot jar.
On 22 December 2017 at 23:17, Ralph Goers
wrote:
> I ran the build again and this time it succeeded. I didn’t get the OSGi
> error you are seeing.
>
I ran the build again and this time it succeeded. I didn’t get the OSGi error
you are seeing.
Ralph
> On Dec 22, 2017, at 4:07 PM, Gary Gregory wrote:
>
> Arg. Tests pass for me in log4j-api. When I run 'mvn clean install', the
> build blows up in log4j-osgi:
>
> ERROR StatusLogger No log4j2
Arg. Tests pass for me in log4j-api. When I run 'mvn clean install', the
build blows up in log4j-osgi:
ERROR StatusLogger No log4j2 configuration file found. Using default
configuration: logging only errors to the console. Set system property
'log4j2.debug' to show Log4j2 internal initialization l
I reported that the build failed for me 2 weeks ago and never heard anything. I
just tried it again and now I get a failure in log4j-api. I can’t perform
releases while there are build failures.
[ERROR] Tests run: 53, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.929
s <<< FAILURE! - in o
Time to release? We have small set of changes that fits in a maintenance
x.x.1 release.
Gary
11 matches
Mail list logo
