davsclaus opened a new pull request, #29824:
URL: https://github.com/apache/camel/pull/29824

   ## Summary
   
   Item 9 of [CAMEL-26912](https://issues.apache.org/jira/browse/CAMEL-26912): 
**two problems of the Camel CLI on Windows** (found by reading the code; not 
run on Windows).
   
   ### 1. A drive letter is taken for a scheme
   
   `Exporter.getScheme` and `CamelCommand.getScheme` return the text before the 
first `:`, so for `C:\certs\keystore.jks` the scheme is `C`:
   
   - the export strips the "scheme" from the files of the run settings, and 
copies `\certs\keystore.jks`, which is not the file: an absolute TLS, classpath 
or JKube file was dropped from the exported project
   - `camel dependency list C:\work\project`, `camel kubernetes run` and `camel 
kubernetes export` of a directory given with its drive did not see it as a 
directory
   
   A single letter is now a drive, not a scheme, as `Run.localPath` already has 
it. Camel has no scheme of one letter.
   
   ### 2. mvn is not found
   
   `MavenCommand.of` (the build of `camel run --runtime=...` and `camel debug`) 
uses the Maven wrapper of the project, and otherwise `mvn`. A process cannot be 
started as `mvn` on Windows, where it is `mvn.cmd` (the JDK only adds `.exe`). 
It is now `mvn.cmd` on Windows.
   
   ## Tests
   
   - `ExporterTest.aDriveOfWindowsIsNoScheme`: `classpath:`, `file:C:\...` and 
`github:` keep their scheme; `C:\certs\keystore.jks` and 
`c:/certs/keystore.jks` have none.
   - `MavenCommandTest`: `mvn`, or `mvn.cmd` on Windows, without a wrapper; the 
wrapper when it can run.
   - camel-jbang-run (273 tests), camel-jbang-core and 
camel-jbang-plugin-kubernetes (156 tests) pass locally.
   
   _Claude Code on behalf of Claus Ibsen (davsclaus)_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_012nJsFsjqqFiwroeHRWaKbS
   


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