On Wed, 9 Aug 2017 15:23:23 -0700, Gary Gregory wrote:
I would start by updating the Maven plugins and any third party deps.

For example:

[INFO] --- maven-jgit-buildnumber-plugin:1.2.10:extract-buildnumber
(default) @ commons-math4 ---


org.eclipse.jgit.errors.RevWalkException: Walk failure.

Why not try updating maven-jgit-buildnumber-plugin to the current version?

To which version?
Isn't this supposed to be defined in the "parent"?



On Wed, Aug 9, 2017 at 3:19 PM, Gilles <gil...@harfang.homelinux.org> wrote:

On Wed, 9 Aug 2017 15:46:54 +0100, sebb wrote:

On 9 August 2017 at 13:51, Gilles <gil...@harfang.homelinux.org> wrote:


Build with Java 8 runs fine:

But with Java 7:

Is anyone willing to debug this failure?

1) Bug in maven-jgit-buildnumber-plugin - rather noisy when it cannot
find the current git info

That's not what makes the build fail since it happens in both.

2) Bug in JVM - buffer overflow.

That's the issue.

[I should have mentioned that I had also read the job log,
before posting.]

Both of these could happen with any Java version.

Or is this a hint for making Java 8 the minimum supported
version for the next release?

That is not a valid conclusion from the evidence.

How do you draw that conclusion?

More to the point, my request is: What to do to fix the negative
advertisement for the project which this Travis issue propagates
(see badge):


To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to