When generating the JAXB objects on Windows and we used variables to locate the WSDL like ${project.basedir}, this is then replaced something like "C:\somefolder\", Backslashes then fails on "Could not create the URI from string"
When I then hard code the folder replacing the backslahes with forward slashes then the process works. This is not best practice as each developer would have to change this variables on each build and this will also fail on our CI/CD pipeline as this builds are on Linux and not on windows.
`
When generating the JAXB objects on Windows and we used variables to locate the WSDL like ${project.basedir}, this is then replaced something like "C:\somefolder\", Backslashes then fails on "Could not create the URI from string" When I then hard code the folder replacing the backslahes with forward slashes then the process works. This is not best practice as each developer would have to change this variables on each build and this will also fail on our CI/CD pipeline as this builds are on Linux and not on windows. `
`
if I change it to this then the build works `
`
Surely the process that creates a URI from string should be Windows and Linux compliant. Is this not a bug?