ColinLeeo opened a new issue, #1084: URL: https://github.com/apache/tsfile/issues/1084
## Summary The ASF Jenkins job [`TSFile/Apache TsFile/develop`](https://ci-builds.apache.org/job/TSFile/job/Apache%20TsFile/job/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 `.pom` and `.jar` (HTTP 200), and its parent POM `org.apache:apache:3` is also present. A local build resolves it fine. - **Last green build (#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 (#588, revision `5414aae`) reports:** ``` Artifact 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 [] ``` i.e. the jar is already in the node's local `~/.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.net` repo:** ``` 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:** #1059 (Guava bump), #1060 (snappy-java bump), #1061 (InputStream short-read fix), #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 Maven `settings.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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
