Service-specific config files with module ids with a colon are invalid filenames in Windows
Closed this issue · 2 comments
bertjan commented
The deploy-tools allow for service-specific configuration using a config file with a name equal to the module id (groupid:artifactid).
Filenames with a colon are not supported on Windows.
The previous (vertx2) format with a ~ as group/artifact separator did work on windows.
MarcelTon commented
Do want 👍