[amoeba]

Nightly Java Cookbook CI started failing in https://github.com/apache/arrow-cookbook/actions/runs/38504124957/job/115657570017 with extraneous log output,

Expected:
    column-1    column-2    column-3
    IRAQ    false    42
    JAPAN    false    43
    JORDAN    true    44
    KENYA    true    45
Got:
    SLF4J(W): No SLF4J providers were found.
    SLF4J(W): Defaulting to no-operation (NOP) logger implementation
    SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
    SLF4J(W): Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
    SLF4J(W): Ignoring binding found at [jar:file:/home/runner/.m2/repository/org/slf4j/slf4j-jdk14/1.7.30/slf4j-jdk14-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J(W): See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
    column-1    column-2    column-3
    IRAQ    false    42
    JAPAN    false    43
    JORDAN    true    44
    KENYA    true    45

It looks like a bug got shipped with Maven 3.10 that caused stderr to start showing up in stdout which caused test failures. See https://www.github.com/apache/maven/issues/13380.

This PR tries an agent-suggested approach which runs the doc example directly with java so stdout is clean.

[amoeba]

Testing to see if this fixes https://github.com/apache/arrow-cookbook/actions/runs/38504124957/job/115657570017.

[amoeba]

The SLF4J thing was just a symptom of the real problem which is a change in JLine that Maven picked up: apache/maven#13380.

[amoeba]

This seems to work okay.