Croway opened a new pull request, #28583:
URL: https://github.com/apache/camel/pull/28583
Backport of #26039 to camel-4.22.x.
On 4.22.x, `LauncherHelper` doesn't handle the Spring Boot `jar:nested:`
code-source URL of the launcher fat jar. The launcher jar path is therefore
unknown, and:
- `camel self-update` on a web-installer install always fails with `unable
to determine how the Camel CLI was installed`
- background processes (e.g. `camel run --background`) try to run a `camel`
command that doesn't exist
Clean cherry-pick (`-x`) of 8ffbfa7cc7a0.
Testing:
- `LauncherHelperTest` (new), `InstallDetectorTest` and the `camel-launcher`
tests pass.
- With the built 4.22.3-SNAPSHOT launcher installed in the web-installer
layout in a container:
- unmodified branch: `camel self-update --check` -> `unable to determine
how the Camel CLI was installed`
- with this backport: the install is detected, and `self-update` reaches
the manifest and pin checks (a pinned install reports `this install is pinned
to version ...`)
--
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]
