Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

I'd rather figure out how to make a Jenkinsfile since it's easier to execute multiple pipelines in a single file. I've used it a lot at my work, but I haven't figured out how to use it on builds.a.o since they don't have our in-house Jenkins plugins. On 17 October 2017 at 19:23, Ralph Goers wrote

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

Sorry - of course, you would need to use profiles to make the dependencies be specific to a particular Java version. Ralph > On Oct 17, 2017, at 5:22 PM, Ralph Goers wrote: > > Just clone the Jenkins job and configure it with Java 8. We know it builds > fine with either Java 7 or Java 8. > >

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

Just clone the Jenkins job and configure it with Java 8. We know it builds fine with either Java 7 or Java 8. Ralph > On Oct 17, 2017, at 1:45 PM, Matt Sicker wrote: > > Perhaps it would be useful to figure out how to run tests in parallel: run > against Java 7 with the latest dependencies com

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

Perhaps it would be useful to figure out how to run tests in parallel: run against Java 7 with the latest dependencies compatible there, and a Java 8 test that runs with updated dependencies that require Java 8. This would be primarily useful in Jenkins as I wouldn't want to double the build time f

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

We dropped support for Java 6 in May of 2015. If you look at https://plumbr.eu/blog/java/java-version-and-vendor-data-analyzed-2017-edition you will see that Java 6 had about a 20% market share at that time. That sa

Java 8 Epic in JIRA.

Hi All, FYI, I created a Java 8 epic in JIRA: https://issues.apache.org/jira/browse/LOG4J2-2080 Gary

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

You're welcome. I'm finding that more and more dependencies have updated to Java 8. I'd like to get there sooner rather than later... Gary On Tue, Oct 17, 2017 at 1:58 PM, Matt Sicker wrote: > Thanks for checking this one out. Mockito uses continuous delivery > nowadays, so new versions come o

Re: logging-log4j2 git commit: Update Mockito from 2.10.0 to 2.11.0. Build passes with 'mvn clean install'.

Thanks for checking this one out. Mockito uses continuous delivery nowadays, so new versions come out rather rapidly (i.e., every merge to master makes a new release). On 17 October 2017 at 14:16, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 85b7282bb -> 2313b947

Re: [1/2] logging-log4j2 git commit: Revert "LOG4J2-2060 AbstractDatabaseManager should make a copy of LogEvents before holding references to them: AsyncLogger log events are mutable"

It's all good, easy to revert ;-) On Oct 17, 2017 10:57, "Remko Popma" wrote: > My bad. > > On Wed, Oct 18, 2017 at 12:22 AM, wrote: > > > Repository: logging-log4j2 > > Updated Branches: > > refs/heads/master ff5e664cd -> 247c91d01 > > > > > > Revert "LOG4J2-2060 AbstractDatabaseManager shou

Re: [1/2] logging-log4j2 git commit: Revert "LOG4J2-2060 AbstractDatabaseManager should make a copy of LogEvents before holding references to them: AsyncLogger log events are mutable"

My bad. On Wed, Oct 18, 2017 at 12:22 AM, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master ff5e664cd -> 247c91d01 > > > Revert "LOG4J2-2060 AbstractDatabaseManager should make a copy of > LogEvents before holding references to them: AsyncLogger log events are > mutab