luigidemasi opened a new issue, #195:
URL: https://github.com/apache/camel-kit/issues/195

   ## Description
   
   A migration can select a version that exists for Camel core but has no 
matching Spring Boot BOM or starter. Kit already passes runtime information 
into catalog calls. Resolve the target once and give generation, catalog lookup 
and validation the same platform-specific coordinates. [Migration version 
selection (#51)](https://github.com/apache/camel-kit/issues/51) ยท [Catalog 
version 
binding](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/docs/modules/ROOT/pages/mcp.adoc)
   
   ## Acceptance criteria
   
   - [ ] Represent the selected runtime, Camel version, application BOM 
coordinates, repositories and catalog binding. Distinguish the application BOM 
used in the generated build from the runtime catalog provider used for lookups. 
Reuse existing version pins and project discovery.
   - [ ] Keep observed source-project versions separate from the destination 
chosen for a migration. Ask for an unresolved selection if modules disagree. A 
different target invalidates results obtained for the previous selection.
   - [ ] Test Camel Quarkus and Camel Spring Boot cases, including a core 
version that differs from the runtime's BOM or provider version. Verify that 
the generated POM passes the version check on its first run without manual 
dependency corrections, and that lookup uses the selected catalog. A missing or 
mismatched required catalog must produce an explicit incomplete check.
   
   ## Website impact
   
   Required. Explain target selection, Maven and catalog coordinates, and 
diagnostics in the configuration, migration and MCP documentation.
   
   _AI-generated by Codex on behalf of @luigidemasi._
   


-- 
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]

Reply via email to