title: Run different ActiveMQ Artemis versions with separate JDK's
body: <p>quick question; is it possible and reasonable to run different Artemis ActiveMQ versions with different JDK versions?
  There are currently two separate Artemis-Services on my VM running different Artemis versions (2.4.0 not cool, I know :/ and 2.16.0).
  Now I want to upgrade the 2.16.0 to 2.21.0 which would mean, that I also need a new JDK version. The problem is I still have to provide a customer with the 2.4.0 version.
  Can I run the 2.21.0 with JDK 17 and the 2.4.0 still with JDK 8?</p>
  <p>The Java-Version seems to be referenced in the artemis-service.xml as %JAVA_HOME% which is a windows environment variable and outputs either JDK 17 or JDK 8.
  Could I just switch this variable to a local env, similar to ARTEMIS_INSTANCE in the artemis-service.xml or is this not an intended use?</p>
  <p>So the new artemis-service.xml would look something like this:</p>
  <pre><code>...
  &lt;env name=&quot;ARTEMIS_INSTANCE_ETC_URI&quot; value=&quot;file:/C:/ApacheMQ/BROKER/etc/&quot;/&gt;
  &lt;env name=&quot;ARTEMIS_DATA_DIR&quot; value=&quot;C:\ApacheMQ\BROKER\data&quot;/&gt;
  &lt;env name=&quot;JAVA_V17&quot; value=&quot;C:\PATH_TO_JDK_17&quot;/&gt;
  
  &lt;logpath&gt;C:\ApacheMQ\BROKER\log&lt;/logpath&gt;
  &lt;logmode&gt;roll&lt;/logmode&gt;
  
  &lt;executable&gt;%JAVA_V17%\bin\java.exe&lt;/executable&gt;
  ...
  </code></pre>
  <p>Obviously one of the JDK versions wouldn't be properly installed but just residing in a folder.</p>
  <p>Yes, I know this is more of a dirty workaround, but would it be an option in principle?</p>