[Doc][Java] Java doc build broken

[asfimport]

See https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=3585&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181

We should either fix the Java doc build or disable building the Java docs.
Personally, I'd be fine with disabling the Java docs if a maintainer doesn't show up.

Reporter: Antoine Pitrou / @pitrou
Assignee: Nicola Crane / @thisisnic

_{Note: This issue was originally created as ARROW-12377. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
@emkornfield [~fan_li_ya]

[asfimport]

Micah Kornfield / @emkornfield:
sorry did not get a chance to look tonight.  Will try to make more time tomorrow.  Or if you have bandwidth [~liyafan]  to look at the failure let me know.

[asfimport]

Liya Fan / @liyafan82:
The build failed because:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project arrow-performance: SiteToolException: ArtifactResolutionException: Unable to find skin: Could not transfer artifact org.apache.maven.skins:maven-default-skin:jar:1.0 from/to central (https://repo.maven.apache.org/maven2): Connection timed out (Read failed)

which means it could not get the jar from the apache maven repository (and it took 15 minutes before timing out).

I just checked the repository (https://repo.maven.apache.org/maven2/org/apache/maven/skins/maven-default-skin/1.0/), and the jar is there.
So I guess this is a temporary network issue, and should go away after retry?

[asfimport]

Joris Van den Bossche / @jorisvandenbossche:
The build is already failing for a long time in the nightly builds as well, so probably not a temporary network issue I think

[asfimport]

Krisztian Szucs / @kszucs:
I won't block the release on this, we can address this issue after or during the VOTE as well.

[asfimport]

Mauricio 'Pachá' Vargas Sepúlveda / @pachadotdev:
this is also mentioned here : https://issues.apache.org/jira/browse/ARROW-11633

[asfimport]

Hans-Joachim Bothe:
It looks like the error analyzed by Liya Fan on Apr 15 is gone. That was probably a missing dependency definition "skins" in java/performance/pom.xml artifact arrow-performance, which could have been loaded from Maven Central and inserted. The mentioned link (https://repo.maven.apache.org/maven2/org/apache/maven/skins/maven-default-skin/1.0/) was already correct, but the dependency was not listed in the dependencies of the artifact and not automatically downloaded. Now, this dependency seems to get solved automatically. Probably due to a newer Maven version.

But there is a new reason for failure now:

The following packages have unmet dependencies:     
r-base : Depends: r-recommended (= 4.0.5-1.2010.0) but 4.1.0
 
This is the same error I can reproduce on my machine. Under Ubuntu 20.10 I could resolve the problem by removing the version number of r-base in ./ci/docker/linux-apt-docs.dockerfile:

changed line 54 from:
r-base=${r}* \

to:
r-base
 
No clue, whether this is the right place for the fix, that's why I didn't make a pull request. I am new here.

[asfimport]

Alessandro Molina / @amol-:
Closing as fixed by comment from @jonkeane on Zulip

Jonathan Keane
Looking at that last message sounds a lot like issues that Nic solved when they were getting R 4.0 + 4.1 into CI. There was a slight massaging we needed when 4.1 was released to connect to the right ubuntu package repostiroy for 4.1