Notice:
* an over 3-minute gap between the first two entries above--neither the
command reader thread nor the pingJob had a chance to run.
* the command reader thread and the ping job executor evidently get a
chance to run from 19:18:02 to 19:19:19. They ran with increased frequency
during that
Thanks Tibor. I'll use `encodeAndWriteToOutput` later. For now, I hacked
together some temporary changes to ForkedBooter so that it "logs" (just
`System.out.println`) the current time every time:
- the command reader thread reads a NOOP via stdin,
- it starts the ping job,
- it checks
>> is there an -Xmx value you would recommend to ensure the parent process
can send the NOOP to the surefire process?
no such value is generic value to recommend. Each application or test must
find our the value to prevent from OOM.
>> I'm making a custom build of surefire-booter to workaround
To clarify, this is the image ours is based on:
https://hub.docker.com/_/alpine; we are not using a vanilla Maven image as
we have to add a few other items to this image as well. I don't know who
maintains that or adds /etc/mavenrc; I'll bring that up in another topic in
another forum. I was just
Hello Chris,
Maybe true of maven-war-plugin
can help?
On Fri, 22 Mar 2019 at 20:12, Christofer Dutz
wrote:
> Hi,
>
> we are currently having a little problem with our build.
> A user complained about not being able to build with a “mvn compile”.
> The reason is that we have one module that
Hi,
we are currently having a little problem with our build.
A user complained about not being able to build with a “mvn compile”.
The reason is that we have one module that builds a web-client (bundled as war)
and a server module to which the client is copied.
We are using the
The base images are developed in https://github.com/carlossg/docker-maven,
right?
Who creates "/etc/mavenrc"?
On Thu, Mar 21, 2019 at 12:05 AM Jason Young
wrote:
> Mikael, sorry I do not appear to have permission to view the link.
>
> I did some digging in the last couple of days. I see that