luigidemasi opened a new issue, #19: URL: https://github.com/apache/camel-kit/issues/19
> Imported from [luigidemasi/camel-kit#28](https://github.com/luigidemasi/camel-kit/issues/28), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-05-02. > Closed by [luigidemasi/camel-kit#29](https://github.com/luigidemasi/camel-kit/pull/29), merged on 2026-05-02. --- ## Description Several skill Markdown files contain hardcoded Quarkus platform BOM versions instead of using placeholder tokens from `distribution.properties`. When `distribution.properties` is updated, these hardcoded values become stale, causing camel-kit to generate projects with incorrect Quarkus platform versions. Currently `distribution.properties` has `quarkus.platform.4.18.0=3.33.1`, but the following files still show `3.33.0`: | File | Line | Value | |------|------|-------| | `skills/camel-brainstorm/guides/version-selection.md` | 69 | `3.33.0` in mapping table | | `skills/camel-brainstorm/guides/version-selection.md` | 91 | `3.33.0` in example block | | `skills/shared/mcp-setup.md` | 72 | `3.33.0` in example block | | `skills/camel-implement/guides/pom-quarkus.md` | 74 | `3.33.0` in example block | ## Root Cause `version-selection.md` already uses `{QUARKUS_PLATFORM_VERSION}` placeholders in some places (line 59), but the mapping table at lines 67-70 and the example blocks in other files use hardcoded values that the LLM reads and follows literally. ## Proposed Fix Replace all hardcoded Quarkus platform versions in skill files with placeholder tokens (e.g. `{QUARKUS_PLATFORM_VERSION}`) that are substituted from `distribution.properties` at runtime. For the mapping table, generate it dynamically from the `quarkus.platform.*` keys. This ensures `distribution.properties` remains the single source of truth. -- 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]
