luigidemasi commented on issue #59: URL: https://github.com/apache/camel-kit/issues/59#issuecomment-6336855718
> Comment by [luigidemasi](https://github.com/luigidemasi) on 2026-07-11 ([original](https://github.com/luigidemasi/camel-kit/issues/98#issuecomment-4946554367)). --- > :robot: **Note:** This triage was generated by a coding agent and should be reviewed by a human maintainer before acting on it. ## Maintainer triage update ### Reproduction - **Verdict:** reproduced on current `main` - **Environment:** `jbangdev/jbang-action:0.139.3`, isolated `HOME`, `JBANG_DIR`, and initially empty Maven cache; no host directories or caches mounted - **Command:** `jbang app install --name camel-kit --fresh camel-kit@luigidemasi/camel-kit` - **Result:** exit code 1 with `Could not read artifact descriptor for io.github.luigidemasi:camel-kit-core:jar:0.3.2-SNAPSHOT` The same clean installation succeeds and reports `0.3.2-SNAPSHOT` when Central Portal Snapshots is supplied explicitly, confirming that the published artifact is available remotely. ### Root cause Snapshots are deployed to: ```text https://central.sonatype.com/repository/maven-snapshots/ ``` However, `camel-kit-main/src/main/jbang/main/CamelKit.java` currently declares only Maven Central releases and Apache snapshots in `//REPOS`. A new user following the documented installation command therefore cannot discover `camel-kit-core:0.3.2-SNAPSHOT` unless they already built it locally or know to provide an additional repository flag. ### Classification - **Type:** bug - **Affected component:** `camel-kit-main` JBang launcher - **Priority:** high — this blocks the documented first-time installation path for every cache-free user - **Duplicates:** none found - **Related work:** luigidemasi/camel-kit#138 and luigidemasi/camel-kit#139 publish the snapshots but do not configure the consumer-side JBang launcher - **Recommended disposition:** accept and fix ### Acceptance criteria - Add `https://central.sonatype.com/repository/maven-snapshots/` to the launcher's `//REPOS` directive while retaining the existing repositories. - From a clean environment with no pre-populated local artifacts, the documented command succeeds without `--repos` or a local source build: ```bash jbang app install camel-kit@luigidemasi/camel-kit camel-kit --version ``` - `camel-kit --version` reports the expected published snapshot version. - Add a post-deployment clean-container consumer smoke test so a published snapshot is not considered usable until the zero-configuration install path succeeds. If repository propagation is delayed, retry the entire disposable container so failed metadata is not reused from cache. - Do not document an extra repository flag as the normal user workflow; the launcher should carry the repository required by its own default dependency. ### Website impact **Not required.** This restores the already-documented zero-configuration JBang installation behavior rather than introducing a new public workflow. -- 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]
