Switch to Maven Artifact Resolver Ant tasks

[sbesson]

The ongoing effort to support Java 17 (#3815) in Bio-Formats highlighted issues with the Maven Ant Tasks component which is used by the Ant build system to retrieve the dependencies from the POM files. More specifically, the upgrade to org.openmicroscopy:ome-codecs:0.4.0 to consume ome/ome-codecs#23 fails with the following stack trace:

[artifact:dependencies] Downloading: io/airlift/aircompressor/0.21/aircompressor-0.21.pom from repository central at https://repo.maven.apache.org/maven2
[artifact:dependencies] Transferring 6K from central
[artifact:dependencies] Downloading: io/airlift/airbase/112/airbase-112.pom from repository central at https://repo.maven.apache.org/maven2
[artifact:dependencies] Transferring 67K from central
[artifact:dependencies] Downloading: org/junit/junit-bom/5.8.0-M1/junit-bom-5.8.0-M1.pom from repository central at http://repo1.maven.org/maven2
[artifact:dependencies] Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/junit/junit-bom/5.8.0-M1/junit-bom-5.8.0-M1.pom
Warning: :dependencies] [WARNING] Unable to get resource 'org.junit:junit-bom:pom:5.8.0-M1' from repository central (http://repo1.maven.org/maven2): Error transferring file: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/junit/junit-bom/5.8.0-M1/junit-bom-5.8.0-M1.pom

The Maven Ant Tasks component has been retired in 2014 and it's almost unexpected that we have been able to use it for so long without issues. This leaves two options to resolve this build problem:

• upgrade Maven Ant Tasks to its official replacement Maven Artifact Resolver Ant Tasks
• drop the Ant build system completely

Although retiring the Ant build system comes up periodically in discussions with @ome/formats team, my primary concern is that it is still not properly scoped but we know retiring it will impact developers, CI and release process minimally. While for several components there is a large overlap of the Ant tasks with the standard Maven lifecycle, there are a number of critical tasks which are currently only defined in Ant including the generation of various archives/bundles (bftools, bfmatlab) and the running of the automated tests.

This PR investigates the first option to modernize the Ant dependency management using Maven-compatible tools and allow us to deliver Java 17 support.

Overall, the changes should be straightforward:

• the maven-ant-tasks is replaced by the maven-resolver-ant-tasks uberJAR and declared in the appropriate Ant configuration files
• the mvn-init task that was using artifacts:dependencies to create compile/test/runtime classpaths is retired and resolver:resolve is directly involved in the compile and compile-tests tasks. The compile.classpath, test.classpath and runtime.classpath` references should remain unchanged
• artifact:install is retired in favor of resolver:artifacts and resolver:install
• the bundle creation is done by first unzipping the runtime.classpath in a temporary build directory and then rezipping it using zipfileset, primarily for performance reasons

[dgault]

The overall approach looks sensible to me, happy to see it removed from draft and included in the CI

[melissalinkert]

Quick test of ant clean jars tools, showinf with the resulting artifacts, and ant ... test-automated on a directory with many datasets seems fine. I don't have any immediate concerns, so fine with taking this out of draft for inclusion in the merge builds.

[sbesson]

One failure in the daily CI build - see https://merge-ci.openmicroscopy.org/jenkins/job/BIOFORMATS-image/1394/console

BUILD FAILED
/bio-formats-build/bioformats/ant/toplevel.xml:288: The following error occurred while executing this line:
/bio-formats-build/bioformats/ant/java.xml:48: Could not resolve artifacts: Could not find artifact org.kohsuke:file-leak-detector:jar:jar-with-dependencies:1.15 in central (https://repo1.maven.org/maven2/)

It's effectively a side-product of the interaction of this PR and #3815 where file-leak-detector is bumped to the next version, requiring the addition of another remote repository in bf047fb.
f06d32a should pre-emptively address this scenario by declaring the repository in ant/java.xml.

[dgault]

All the changes here look to be sensible and the PR has been included as part of the CI for a while now without issues. I manually tested each of the main ant targets and the results were as expected. All the generated artefacts match those produced without the PR and tests all run without issue. PR is good to merge from my side.