[
https://issues.apache.org/jira/browse/MRM-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574367#comment-17574367
]
David Newcomb commented on MRM-2031:
------------------------------------
I've just tried to run Archiva 2.2.8 with java 11 and the whole thing blows up
with ClassNotFoundExceptions due to the afore mentioned javax.xml. Jaxb needs
to be bundled in but even after that something else goes wrong in the bean
creation. So I've just spent the day getting java8 onto a Debian10 and it seems
happier now.
To correct [~bvd] (or add to his statement) the EE interfaces were bundled in
with java8 and available by default, java9/10 it was bundled in but you needed
command line options to switch on the packages you wanted, but in java11 it has
all been completely removed so it has to be provided externally. Which is why
it was such a pain to try and fix it. You have to... I won't bore you with the
details but it was a pain which ultimately I couldn't do so I had to waste the
rest of the day trying to get java8 on there which was also not as easy as it
sounds because it's really old.
(Cloud images of) Linux and there associated distros have just moved to java11
by default, so if you could keep the minimum at java11 that would make things
just a bit easier :)
Can we bump the priority on this a bit as it's not strictly an improvement any
more, it's a system-down bug in the application and the documentation is out of
date. Sorry, it was such a pain getting java8 on there and there was no help
anywhere on your site.
> Switch to JDK 11
> ----------------
>
> Key: MRM-2031
> URL: https://issues.apache.org/jira/browse/MRM-2031
> Project: Archiva
> Issue Type: Improvement
> Reporter: Martin Schreier
> Assignee: Martin Schreier
> Priority: Major
> Fix For: 3.0.0
>
>
> We should use JDK 11 as baseline, if the libraries and build process work.
> This is possible only after switching to Jakarta EE 9.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
