release_version.sh currently failing bc of unavailable javadoc resources

[k-dominik]

Dear Scijava team,

I was trying to bump the version for the ilastik fiji plugin, and it fails during javadoc run because of some missing unrelated resources (omero, bio-formats). Would it be possible to add a switch to the script to skip javadoc run, or is it required to release a new version?

Cheers
Dominik

[ctrueden]

@k-dominik Thanks for the report. We could potentially add a flag to skip the javadoc build, but you would then not have a foo-x.y.z-javadoc.jar deployed to the Maven repository for that release, which would be unfortunate.

For individual resource outages, we can fix it by changing the served javadoc from a proxy/reverse-proxy to an internally served resource, so that when e.g. OME servers go down, it doesn't break SciJava release builds.

See scijava/pom-scijava#130 for details on how I'm working toward a real solution to this issue for the long term.

[ctrueden]

I'm going to close this as "not planned" because I don't want releases skipping the javadoc build. You can instead pester me to work on scijava/pom-scijava#130 so that this problem stops happening. 😅