smongiar opened a new pull request, #30221: URL: https://github.com/apache/camel/pull/30221
When exporting from the executable Camel launcher, `java.class.path` contains only the outer launcher JAR. Kamelets version detection therefore falls back to the build-time default even when a different catalog is bundled inside the launcher, and the generated POM uses the wrong version. Read the bundled catalog's Maven `pom.properties` before using the fallback. Existing filename-based detection and explicit `--kamelets-version` selection retain their behavior. Add four regression tests and an upgrade-guide note describing the export behavior. Validation: - The metadata detection regression fails against the original helper; all four tests pass with the fix in a focused Maven harness using released dependencies. - The packaged launcher exports the bundled Kamelets version after the fix. Regular classpath export and explicit version selection also pass. - Camel's Eclipse formatter and import sorter checks pass. The full Camel reactor was not built locally. -- 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]
