If Jenkins is configured to do "mvn clean" first, then the only time it
could save is in downloading dependencies. I usually set up my own Jenkins
jobs using "mvn verify" or "./gradlew build" or equivalent, though it tends
to work better with Gradle in the past (incremental compilation with Maven
m
It just occurred to me that maybe the build took longer than normal because
this was the first time a standalone build for 3.x was run. I’ll review it
again after it builds a few more times.
Ralph
> On Feb 18, 2018, at 12:20 PM, Gary Gregory wrote:
>
> On Sun, Feb 18, 2018 at 12:44 AM, Ralph
On Sun, Feb 18, 2018 at 12:44 AM, Ralph Goers
wrote:
> While splitting out components into modules should have had the desired
> effect of reducing the dependencies in log4j-core, it didn’t help making
> the builds take less time. The Jenkins build for 3.x took about 43 minutes
> while the 2.x b
While splitting out components into modules should have had the desired effect
of reducing the dependencies in log4j-core, it didn’t help making the builds
take less time. The Jenkins build for 3.x took about 43 minutes while the 2.x
build took 38 minutes.
Ralph
