Croway commented on PR #28581: URL: https://github.com/apache/camel/pull/28581#issuecomment-6464947879
Thanks @davsclaus (and gnodet-bot), both addressed in 5026ff58962b (ported to #28584 as fbd4ed7ee2f9): 1. **Nearest older selection.** The range is still stored, and an `Older` selection now also stores the Camel version it was selected for (`"selectedForCamel": "4.21"`). The load-time check stays quiet while the CLI is on that Camel version, since `plugin add` already warned. Once the CLI moves to another Camel version, the usual warning comes back, and re-running `camel plugin add` can then pick a matching release. `PluginAddTest` asserts the stored entry, and a new `PluginHelperTest` case covers no warning on the same Camel version and a warning on the next one. 2. **Failed POM read.** When the POM of the newest release of a line cannot be read, the next release of the same line is read, and each try still counts against the cap. New test `fallsBackToTheNextReleaseOfTheLineWhenAPomCannotBeRead`: 2.0.1 is listed but unreadable, and 2.0.0 is selected. `PluginVersionResolverTest`, `PluginAddTest`, `PluginHelperTest` and `PluginCompatibilityTest` pass on both branches (65 tests, 0 failures). -- 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]
