What is the expected behavior?
The references to the files containing dependencies of the main RAML file are resolved on Windows as they are on Linux systems.
What is the motivation/use case for changing the behavior? (for feature requests)
I'm building a SonarQube plugin to analyze MuleSoft projects.
Please tell us about your environment:
AMF Version: 5.5.1 also tested on 5.4.9
AMF Distribution: JVM
Operating System: Windows 11, Ubuntu 22.04
Link to your project:
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, Gitter, etc)
The above code is meant to convert RAML 1.0 to OAS 3.0. It fully performs as is expected when executed in Linux, but in Windows the resulting document does not include any of the RAML children files' data.
I have tried switching the dashes in the RAML '!include ' statements to backslashes '\' for Windows paths. However, the result is the same.
Your issue may already be reported! Please search on Github issues before creating one.
I'm submitting a ...
What is the current behavior? RAML file references are correctly resolved in Linux but not in Windows.
If the current behavior is a bug, please provide the minimal steps to reproduce with AMF code. Please don't upload AMF code mixed with yours.
What is the expected behavior? The references to the files containing dependencies of the main RAML file are resolved on Windows as they are on Linux systems.
What is the motivation/use case for changing the behavior? (for feature requests) I'm building a SonarQube plugin to analyze MuleSoft projects.
Please tell us about your environment:
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, Gitter, etc) The above code is meant to convert RAML 1.0 to OAS 3.0. It fully performs as is expected when executed in Linux, but in Windows the resulting document does not include any of the RAML children files' data. I have tried switching the dashes in the RAML '!include ' statements to backslashes '\' for Windows paths. However, the result is the same.