Repository navigation
Description
Summary
The ASF Jenkins job TSFile/Apache TsFile/develop has been failing consistently since build #588 (currently #588–#594). The failure is a Maven dependency resolution error in the tsfile module's generate-fmpp (Freemarker codegen) step — it can no longer resolve the legacy artifact xml-resolver:xml-resolver:1.2.
This is an infrastructure/repository-configuration regression on the CI node, not a code bug in the repository.
Error
Failed to execute goal org.apache.drill.tools:drill-fmpp-maven-plugin:1.21.1:generate
(generate-fmpp) on project tsfile:
Plugin org.apache.drill.tools:drill-fmpp-maven-plugin:1.21.1 or one of its dependencies
could not be resolved:
Could not find artifact xml-resolver:xml-resolver:jar:1.2
Dependency chain:
drill-fmpp-maven-plugin:1.21.1 → com.googlecode.fmpp-maven-plugin → net.sourceforge.fmpp:fmpp → xml-resolver:xml-resolver:1.2
The plugin is declared at pom.xml (drill.freemarker.maven.plugin.version = 1.21.1) and used in java/tsfile/pom.xml under the generate-fmpp execution.
Evidence that this is a CI-side regression, not a code change
- The artifact exists on Maven Central.
https://repo1.maven.org/maven2/xml-resolver/xml-resolver/1.2/serves both the.pomand.jar(HTTP 200), and its parent POMorg.apache:apache:3is also present. A local build resolves it fine. - Last green build (Bump actions/first-interaction from 1.3.0 to 3.0.0 #586, revision
931a5d3) downloaded it from central:Downloaded from central: https://repo.maven.apache.org/maven2/xml-resolver/xml-resolver/maven-metadata.xml - First failing build (Alter column other type to string type #588, revision
5414aae) reports:i.e. the jar is already in the node's localArtifact xml-resolver:xml-resolver:jar:1.2 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from []~/.m2, but its cached provenance ("remote repository ID") no longer matches any repository available in the current build, so Maven re-verifies against an empty list and reports it as missing. - Every failing run also logs a TLS failure against the long-dead
maven.java.netrepo:Could not transfer metadata ... from/to jvnet-nexus-releases (https://maven.java.net/content/repositories/releases/): PKIX path validation failed: ... validity check failed - The commits between the two revisions are unrelated to FMPP/xml-resolver: build(deps): bump com.google.guava:guava from 33.5.0-jre to 33.7.1-jre in /java #1059 (Guava bump), build(deps): bump org.xerial.snappy:snappy-java from 1.1.10.5 to 1.1.10.9 in /java #1060 (snappy-java bump), Handle short reads from InputStream #1061 (InputStream short-read fix), [Python] Add ASan/LSan coverage for bindings and C++ integration #1047 (Python ASan/LSan coverage). The FMPP plugin has been in the build since 2024-08.
- The repository's POMs declare no
<repositories>/<pluginRepositories>, so the repository list comes entirely from the Jenkins node's Mavensettings.xml.
Conclusion / what's needed
The ASF Jenkins Maven configuration changed around builds #587/#588, and the current repository list can no longer resolve the legacy xml-resolver:xml-resolver:1.2 artifact (which only lives on Maven Central). This needs an ASF INFRA fix to the job's Maven settings — remove/repair the dead maven.java.net (jvnet-nexus-releases) repository entry and ensure central (or a mirror that proxies it) is available for plugin dependency resolution.
Possible repo-side mitigation (if INFRA is slow): explicitly declare a pluginRepositories entry for Maven Central so the FMPP plugin's dependencies resolve from repo.maven.apache.org regardless of the node's settings.
Activity
[-]ASF Jenkins `develop` builds failing: cannot resolve `xml-resolver:xml-resolver:1.2` in `generate-fmpp`[/-][+]ASF Jenkins develop builds failing: cannot resolve xml-resolver:xml-resolver:1.2 in generate-fmpp[/+]HTHou commentedon Nov 10, 2026
Thanks for digging into this. Could you open a ticket in ASF INFRA Jira and ask the Infra team to check whether the Maven repository or mirror settings changed for the TsFile
developJenkins job around build #588? Please include a link to this issue in the ticket and share the Jira link here so we can follow up.ColinLeeo commentedon Nov 10, 2026
Superseded — root cause is the ASF Jenkins node's Maven settings.xml (dead maven.java.net / jvnet-nexus-releases repo with an invalid TLS cert; xml-resolver:xml-resolver:1.2 cached provenance no longer resolvable), which only ASF INFRA can fix. Filing under ASF INFRA JIRA (project INFRA) instead.