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

   ## Description
   
   Camel Kit already recognizes Mule, BizTalk, older Apache Camel and Fuse 
projects. Make each migration family responsible for its own source detection, 
guides, parser integrations and version-specific rules. Developers should 
continue to reach these migrations through their existing commands. [Supported 
migrations](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/docs/modules/ROOT/pages/migration.adoc)
 · [Camel and Fuse upgrade 
workflow](https://github.com/apache/camel-kit/blob/79f145c6ebe41dbfdf05a505fca4e357b8ec4caf/docs/modules/ROOT/pages/migration-camel-upgrade.adoc)
 · [Direct migration mode 
(#105)](https://github.com/apache/camel-kit/issues/105)
   
   ## Acceptance criteria
   
   - [ ] Convert Mule first and keep it enabled by default. Compare 
representative inputs, generated artifacts, graph semantics and diagnostics 
before and after extraction. Invoke the same public hooks another migration 
would use.
   - [ ] Add a BizTalk pack, one Camel upgrade pack for Camel 2.x and 3.x to 
Camel 4, and one Fuse pack for Fuse 6.x and 7.x. Test both starting versions 
separately in the Camel and Fuse packs. Shared helpers must preserve 
source-specific behavior.
   - [ ] Select one migration and its source scope per run. Test a mixed 
Mule/BizTalk directory and a Fuse project with Camel dependencies. When 
evidence is ambiguous, ask for a choice and retain the other candidates. 
Preserve both guided and direct migration modes.
   
   ## Website impact
   
   Required. Update the migration overview and the Mule, BizTalk and Camel/Fuse 
guides with discovery, scope selection and examples.
   
   _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