rovshan-b opened a new issue, #70000: URL: https://github.com/apache/doris/issues/70000
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version master, branch-4.1 and branch-4.0 (all pin `<je.version>18.3.14-doris-SNAPSHOT</je.version>` in `fe/pom.xml`). Observed on a 4.1.5 checkout with an unchanged `fe/pom.xml`. ### What's Wrong? Since 2026-11-02 a Frontend build with an empty (or expired) local Maven repository fails to resolve `org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT`: ``` [ERROR] Failed to execute goal on project fe-core: Could not resolve dependencies for project org.apache.doris:fe-core:jar:1.2-SNAPSHOT [ERROR] dependency: org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT (compile) [ERROR] Could not find artifact org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT in central (https://repo.maven.apache.org/maven2) [ERROR] Could not find artifact org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT in huawei-obs-sdk (https://repo.huaweicloud.com/repository/maven/huaweicloudsdk/) [ERROR] Could not find artifact org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT in snapshots (https://repository.apache.org/content/repositories/snapshots/) [ERROR] Could not find artifact org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots) ``` The artifact only ever existed in the Apache snapshot repository. That repository keeps a single snapshot version per artifact: `https://repository.apache.org/content/repositories/snapshots/org/apache/doris/je/` now lists only `18.3.17-doris-SNAPSHOT` (uploaded 2026-11-02 06:36 UTC), and `18.3.14-doris-SNAPSHOT/maven-metadata.xml` returns 404. `je` is not published anywhere else, including Maven Central. Machines and CI runners that built before still have the jar in `~/.m2`, so the breakage only shows on a fresh environment. That is probably why it has not been noticed yet. ### What You Expected? `fe/pom.xml` resolves on a clean machine, either by pinning the snapshot that is currently published (`18.3.17-doris-SNAPSHOT` resolves today) or, better, by depending on a released, non-snapshot build of `je` so this cannot repeat the next time the snapshot rotates. ### How to Reproduce? With an empty local repository, no project needed: ``` cd "$(mktemp -d)" mvn -B -Dmaven.repo.local="$PWD/m2" dependency:get \ -Dartifact=org.apache.doris:je:18.3.14-doris-SNAPSHOT \ -DremoteRepositories=apache.snapshots::::https://repository.apache.org/content/repositories/snapshots/ # -> Could not find artifact org.apache.doris:je:jar:18.3.14-doris-SNAPSHOT in apache.snapshots mvn -B -Dmaven.repo.local="$PWD/m2" dependency:get \ -Dartifact=org.apache.doris:je:18.3.17-doris-SNAPSHOT \ -DremoteRepositories=apache.snapshots::::https://repository.apache.org/content/repositories/snapshots/ # -> succeeds ``` Or clone the repository on a machine that has never built Doris and run the FE build. ### Anything Else? Bumping `je.version` to `18.3.17-doris-SNAPSHOT` builds and passes FE unit tests here (checked the `org/apache/doris/catalog/**/*Test` pattern, 477 tests), so a one-line bump unblocks fresh builds immediately. A released version would be the durable fix. ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
