I’m back to making another attempt at building. :-) I am not able to update my development machine to use java 11, so I am trying with docker like this:
docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-openjdk-11 mvn clean install But I quickly run into this problem: [INFO] Apache James :: Testing :: Base .................... FAILURE [ 38.634 s] [ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.1:revision (get-the-git-infos) on project testing-base: Could not complete Mojo execution...: GIT-Command 'git describe --dirty=-dirty --match=* --abbrev=7' did not finish in 30000 milliseconds -> [Help 1] The plugin doesn’t seem to work in this environment, so I skipped it by adding `-Dmaven.gitcommitid.skip=true` to the run parameters. Q: Will this cause any problems once I can eventually build successfully? New result: [INFO] Apache James Cassandra backend ..................... FAILURE [ 57.902 s] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project apache-james-backends-cassandra: There are test failures. [ERROR] [ERROR] Please refer to /usr/src/mymaven/backends-common/cassandra/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. So I disabled tests and tried again. The build continues almost to the end (60 minutes on my machine), and unfortunately ends with this: [INFO] Apache James :: Server :: Web Admin server integration tests :: Common FAILURE [ 12.443 s] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-webadmin-integration-test-common: Compilation failure: Compilation failure: [ERROR] /usr/src/mymaven/server/protocols/webadmin-integration-test/webadmin-integration-test-common/src/main/java/org/apache/james/webadmin/integration/JwtFilterIntegrationTest.java:[34,33] cannot find symbol [ERROR] symbol: class WebAdminUtils [ERROR] location: package org.apache.james.webadmin Sadly, I still cannot run `mvn eclipse:eclipse`, so I still cannot make any PRs. Looks like I’ll need some help getting started, if that is possible. Cheers, =David > On Apr 27, 2020, at 15:49, David Leangen (Apache) <apa...@leangen.net> wrote: > > Thanks for the clarification. That will push me in the right direction. > > If I ever get it built someday, then I’ll try to remember to submit a PR to > mention the version requirement somewhere in the docs. > > I’ll just concentrate on the pre-built for now version then. > > Cheers, > =David > On Apr 27, 2020 15:44 +0900, Matthieu Baechler <matth...@apache.org>, wrote: >> On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote: >>> Thank you, Rene. >>> >>> Is that a hard requirement? If so, then I will have to wait until we >>> update to Java 11 (which is not scheduled at this time), so I’ll >>> likely have to abandon for now. >>> >>> Shouldn’t it be possible to compile in Java 8, though? This page >>> states that JRE8 is the requirement: >>> >>> —> https://james.apache.org/server/quick-start.html >> >> This guide is about deploying an already-compile James server. >> >> Up to James 3.5 (which has a pending release), you could run with Java >> 8 JRE. >> >> Starting with James 3.6, you'll need Java 11. >> >> What you are trying to do is to compile it yourself, the requirements >> are differents. >> >> For some times now (probably 3.4) we use Java 11 compiler but target >> Java 8. >> >> Cheers, >> >> -- Matthieu Baechler >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >>
