2 ms·

Not sure if you'll catch this message any time soon, but: 1. major source of incompatibility was the removal of the ability to cast ClassLoader to a URLClassLo

Not sure if you'll catch this message any time soon, but: 1. major source of incompatibility was the removal of the ability to cast ClassLoader to a URLClassLoader, fixes for that were relatively extensive but also simple enough to get running in a few days. 2. Not seen any crash reports in the first 24 hours which is a good sign, any that do come up I will forward as bug reports. 3. Perf wise, about equal, memory usage is much better. 4. Thanks for the impetus to give migrating another go.

pron 5y ago
Good! You might want to try using the G1 GC, which is now the default. > major source of incompatibility was the removal of the ability to cast ClassLoader to a URLClassLoader Right. That was an unspecified behaviour, though, that just happened to be true for a long time so people depended on it.
- DarkmSparks 5y ago
  So far so good just default parameters plus an 8gb heap. >unspecified behaviour Also the accepted answer on 100+ different websites for how to choose single jars from a folder at runtime that still compiles but now excepts with no easy replacement or even explanation of how to replace it. If i get time i might write up how i fixed it.
  - pron 5y ago
    > Also the accepted answer on 100+ different websites for how to choose single jars from a folder at runtime Which goes to show that not all information sources are equally good. For a couple of decades, we've said over and over -- and still do -- that depending on unspecified behaviour is technical debt that will eventually break your codebase. > with no easy replacement or even explanation of how to replace it That's how online givers of bad advice roll -- they advise you do something they know is wrong, and when things go south they don't help you; those who followed Sun/Oracle's advice ran into no such issues. There are documented and supported ways to get the classpath. (I won't lie, I used that easy trick, too, once or twice, but I did it knowing full well that it might well stop working some day, and treated it as technical debt.)

pron 5y ago

Good! You might want to try using the G1 GC, which is now the default. > major source of incompatibility was the removal of the ability to cast ClassLoader to a URLClassLoader Right. That was an unspecified behaviour, though, that just happened to be true for a long time so people depended on it.

DarkmSparks 5y ago
So far so good just default parameters plus an 8gb heap. >unspecified behaviour Also the accepted answer on 100+ different websites for how to choose single jars from a folder at runtime that still compiles but now excepts with no easy replacement or even explanation of how to replace it. If i get time i might write up how i fixed it.
- pron 5y ago
  > Also the accepted answer on 100+ different websites for how to choose single jars from a folder at runtime Which goes to show that not all information sources are equally good. For a couple of decades, we've said over and over -- and still do -- that depending on unspecified behaviour is technical debt that will eventually break your codebase. > with no easy replacement or even explanation of how to replace it That's how online givers of bad advice roll -- they advise you do something they know is wrong, and when things go south they don't help you; those who followed Sun/Oracle's advice ran into no such issues. There are documented and supported ways to get the classpath. (I won't lie, I used that easy trick, too, once or twice, but I did it knowing full well that it might well stop working some day, and treated it as technical debt.)