I think the answer might be in the original description that they "can
work around this using Cygwin". Was the instance perhaps also
*initially created* using Cygwin or such to begin with?
That will be detected and so be treated as creation for a *nix
instance, i.e not outputting .cmd files etc. T
I just created a Windows 10 VM, installed OpenJDK 17, downloaded ActiveMQ
Artemis 2.39.0 [1], unzipped it, and created an instance using the same
command you used (except I had to specify a value for --http-host). The
instance's "bin" directory contained "artemis.cmd" and I was able to use it
to ru
Greetings,
It seems that in 2.39, making an instance on Windows doesn't create the
instance\bin\artemis.cmd file that we got under 2.30. We can work around this
using Cygwin, and we don't use Windows in production, but was it removed
intentionally? Did I do something wrong creating the instan
