Skip to content

ASF Jenkins develop builds failing: cannot resolve xml-resolver:xml-resolver:1.2 in generate-fmpp #1084

Closed

Description

@ColinLeeo

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

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

  1. changed the title [-]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[/+] on Nov 10, 2026
  2. HTHou commented on Nov 10, 2026

    @HTHou
    Contributor

    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 develop Jenkins 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.

  3. ColinLeeo commented on Nov 10, 2026

    @ColinLeeo
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions