Hello everyone,
just did a build of 3.8.1 from source and ran into a few quirks:
1) JAVA_HOME has to be set
As many of you know I use OpenSuSE as my main server OS (although from
day to day I reevaluate to stick to it) and until now I used the fresh
system to also compile James from source. Funny enough with all its
quirks I encountered of the years it worked fine with the usual "mvn
clean package -DskipTests".
But as I also did a run on my main system running Arch I ran into an
error due to I had not set JAVA_HOME explicitly.
Guess that's just another one of those "yea, suse does something
different than everyone else". Maybe this could added into the docs if
it isn't already?
2) 3.8.1 requires Java17 to build
Another issue on my Arch system happened due to its way newer Java
version 22. The build fails rather early on within the first few
sub-packages with something related to Scala. I'm not sure how this is
related to each other but as the error also had some lines in it with
"reflections" - well, as a Java dev I know: "When you think about using
reflections you don't need them as you do something way wrong!". So I
guess some changes between Java17 and Java22 lets the Scala compiler
fail fatal.
If someone wants to reproduce:
- set up two VMs: one with OpenSuSE LEAP15.5, the other one with Arch
- clone james-project with branch 3.8.1
- run: mvn clean package -DskipTests
With Java17 suse will build fine, Arch using Java22 fails rather early -
switching to Java17 on Arch gets the build quite far but then fails with
"JAVA_HOME not set" - after setting JAVA_HOME Arch also gets the build done.
So long,
have a nice weekend everyone.
Matt
Greetings from Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
