Hi Ede,Thanks for the downgrade. I don't know how you did find the offending maven plugin.I agree that we should not migrate to java 11 too early. I think that staying on java 8 in 2022 until the second OpenJUMP 2 release would be reasonable, but let's talk about it again when some dependencies w
thanks for the heads up Brian!
keeping java8 compatible is more a courtesy to possibly not even existing users
anymore. as it stands OJ is tested an runs successfully on up to jre17.
..regards ede
@Mike: from my point of view we can wait until the first important core
dependency drops java8 s
Hi JUMP-ers -
I believe at osgeolive linux we have java8 marked as LTSl more info
after March 2022
best regards from Berkeley, Calif. --Brian M Hamlin / OSGeoLive
Linux
On 1/15/22 7:12 AM, Michaud Michael wrote:
Hi Ede,
I cannot compile any more because of a java version conf
we will probably have to upgrade the maven build requirements (that's just the
build not OJ2) at some point when plugins start to drop java8. for now i
downgraded the offending plugin again.
works for me :).. ede
On 15.01.2022 16:25, edgar.sol...@web.de wrote:
run maven with -X. that should g
run maven with -X. that should give plenty more details.
currently still use a java8 to compile OJ2, so i should have seen if there is
an issue ..ede
On 15.01.2022 16:12, Michaud Michael wrote:
Hi Ede,
I cannot compile any more because of a java version conflict 52.0 vs 55.0
(java8 vs java11
