You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by si...@gmail.com on 2022/05/06 12:27:50 UTC
JAXB and Java version issues with Archiva?
Hi, I’ve been away from Archiva, and the Maven community at large for little more than a decade, as my career has taken me in other directions. Now I’ve encountered a renewed need for these, and have just attempted installing Archiva 2.2.7 on an Ubuntu 20.04 machine. On my first attempt, I installed using the modern version of Java (17 or 18) already installed on the machine, and that did not go well. The service started, but not the WebApp, as there were fatal errors logged during initialization of the Spring Beans. The logged Exceptions ended in root causes of ClassNotFoundExceptions, which is diagnoseable, and lead me to the conclusion, that it couldn’t find the JAXB classes, as these were moved around Java 8. I then double-checked the system requirements, that list JDK 1.8 as a requirement and tried installing JDK 8, and trying to run Archiva on that. That didn’t change anything, so I manually tried adding a number of JAXB-related jars as suggested in some stackexchange answer, related to similar JAXB problems. This solved the immediate ClassNotFoundExceptions, but actually made the situation worse, as I now get mile long stacktraces, ending with a root cause of a NullPointerException, which is notoriously hard to troubleshoot without detailed insight into the code.
I’m not entirely sure, but my diagnostics so far has lead me to the following observations:
* The documented JDK version supported by Archiva is no longer fully supported by Oracle, as it is simply too old
* It seems,that Archiva 2.2.7 has never even been tested on the documented Java 8, but only on even older versions even further out of support.
* This leads me to the following big question: Is Apache Archiva still being actively supported and maintained, or have the developers behind it moved on to bigger and better things?
* If Apache Archiva is dead or dying, what is the recommended Maven repository manager today?
Best regards,
Simon Kepp.
RE: JAXB and Java version issues with Archiva?
Posted by si...@gmail.com.
Thanks for the reply. It gave me enough hope to do some more troubleshooting on my end, and it turned out to be, a typical case of EEBKAC (Error Exists Between Keyboard and Chair).
My first installation attempt used OpenJDK Runtime Environment (build 11.0.15+10-Ubuntu-0ubuntu0.20.04.1), which was the latest LTS version available, when I installed the server. I later changed to OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07), but it appears, that some of the hacks, I had done to try to get things working on JDK 11 was causing the problems on JDK 8. After setting it to use JDK 8 and removing my previous hacks for JDK 11, it ended up working fine.
Now, my only problem is, that I am running on JDK 8 for which "Premier Support" or "full support" ran out a few months ago (March 2022). I can live with that in my setup, but suspect, that this could be a deal-breaker for others. I would recommend, that Archiva was updated to support a newer and supported Java version, either Java 11 or preferably Java 17, which are newer LTS releases.
Best Regards,
Simon Kepp.
-----Original Message-----
From: Bram Van Dam <br...@intix.eu>
Sent: Saturday, 7 May 2022 13.13
To: users@archiva.apache.org
Subject: Re: JAXB and Java version issues with Archiva?
> * The documented JDK version supported by Archiva is no longer
> fully supported by Oracle, as it is simply too old
Which exact JDK versions did you try? I have a version running on RHEL with 1.8.0_322 without any issues.
I also just checked out the source and successfully built it on JDK
11.0.15 (Temurin) and on 17.0.3+7 without any significant issues. So I'm guessing this won't be too hard to fix.
> * If Apache Archiva is dead or dying, what is the recommended Maven repository manager today?
It has been pretty quiet on the mailing list for a while, and there haven't been any significant releases in recent times. The team did release a version withe Log4J security fixes, and there are a couple of recent commits on master, so it seems like things aren't entirely dead in the water.
Aside from the user interface, Archiva holds up pretty well, so it would be a shame to see it go.
- Bram
Re: JAXB and Java version issues with Archiva?
Posted by Bram Van Dam <br...@intix.eu>.
> * The documented JDK version supported by Archiva is no longer
> fully supported by Oracle, as it is simply too old
Which exact JDK versions did you try? I have a version running on RHEL
with 1.8.0_322 without any issues.
I also just checked out the source and successfully built it on JDK
11.0.15 (Temurin) and on 17.0.3+7 without any significant issues. So I'm
guessing this won't be too hard to fix.
> * If Apache Archiva is dead or dying, what is the recommended Maven repository manager today?
It has been pretty quiet on the mailing list for a while, and there
haven't been any significant releases in recent times. The team did
release a version withe Log4J security fixes, and there are a couple of
recent commits on master, so it seems like things aren't entirely dead
in the water.
Aside from the user interface, Archiva holds up pretty well, so it would
be a shame to see it go.
- Bram