Christopher Schultz

Can we just change this issue to "require Java 11/17/whatever+" and finally move-on from Java 8?

You would not ask such questions if you looked at the Install4j script that launches Mirth. It appears install4j supports version-specific JVM launch parameters. 😮 I'm a little curious why...

I'm going to ping this issue once again. Seems trivial, and would be very helpful.

As a further clarification, parameter name ordering should be such that the _first_ appearance of the name dictates its position in the enumeration returned by `HttpServletRequest.getParameterNames`. I happen to think...

Perhaps you had a bad download, or a proxy server which delivered the wrong binary to you. Try it again; I haven't had any problems installing Veloedit, including back when...

Yes, it's practically unreadable because Eclipse changes only the background color from white to very dark gray and doesn't update the other colors. So you have e.g. `$foo` in blue-on-dark-gray...

That works great. I didn't know the colors were tweakable from the prefs UI. Thanks for the pointers.

The important part of all of this is being able to _understand what all the tables mean_. It's great to see visually that `d_mm1` and `d_mc1` and `d_ma1` are all...

It would be great to have some additional material nearby / referenced where you can find out the answer to the question "what exactly is message metadata?" versus "what exactly...

I experienced the same issue moving from Mirth 4.1.1 on Java 8 to Mirth 4.4.2 on Java 11 (Amazon Coretto). I have changed the "Default Resource" (aka `custom-lib`) to *parent-first*...