Arch Linux User Repository

Everyone, with great thanks to @SailReal, this package now builds Cryptomator from source. If you wish to continue using the binary AppImage build, you need only to install cryptomator-bin.

We made this change to better align with the desires of the community (you've asked a few times to make this a "build from source" package) as well as better align to the package naming convention within the AUR.

@Munzu makedepends contains now directly jdk17-openjdk which should fix this problem for other users in the future...thanks again for your feedback :)

@Munzu ahhhh, well, I see, you did install a Java runtime environment (jre) and not a Java development kit (jdk), how would you know^^, but for compiling software, we need the jdk. Will change the pre check to verify that a jdk is installed (using javac -version instead of java -version) and check if we can better specify the Java dependency in general because months ago, Arch didn't have an Java version 17 in the official repositories but now it is https://archlinux.org/packages/extra/x86_64/jdk17-openjdk/ ... this will make it even more clear what to install.

Thanks for your feedback and will enhance it soon.

@SailReal Yeah it's weird. I've tried restarting and clearing the paru cache in ~/.cache/paru/clone/cryptomator but no difference. Actually, maybe I should have mentioned this, the same system upgrade I was running (that also resulted in the compilation error) installed jre-openjdk-headless (17.0.4.1.u1-2) and jre-openjdk (17.0.4.1.u1-2) according to the pacman log. It asked me something like whether I want to replace some Java thing with the other. If I remember correctly, the two options were the same name except one didn't have the 17(?) in the name so I just picked the default option which had the more general name. Unfortunately, I don't remember the exact name.

Here's what I think are the relevant lines in my /var/log/pagman.log:

[2022-10-09T10:03:14+0200] [ALPM] installed jre-openjdk-headless (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it
[2022-10-09T10:03:14+0200] [ALPM] installed jre-openjdk (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] when you use a non-reparenting window manager,
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] set _JAVA_AWT_WM_NONREPARENTING=1 in /etc/profile.d/jre.sh
[2022-10-09T10:03:14+0200] [ALPM] installed jdk-openjdk (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it

When I do $ archlinux-java status, I get the following output:

Available Java environments:
  java-11-openjdk
  java-17-openjdk (default)
  java-18-openjdk

EDIT: I had to do $ sudo archlinux-java set java-18-openjdk, now the installation worked. Sorry about the bloated comment.

@Munzu this is weird because Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10. 1:compile (default-compile) on project cryptomator: fatal error compiling: error: release version 17 not supported indicates that you are trying to compile it with Java version pre 17, but during compilation in a pre-check the build script checks the Java version too and would fail if it is not 17 or 18 with another message...what I don`t understand is why the Java binary thinks it is version 17 but fails during compilation because it is not 17?^^ ... does a restart make a difference?

@SailReal I get the following output:

$ java --version
openjdk 17.0.4.1 2022-08-12
OpenJDK Runtime Environment (build 17.0.4.1+1)
OpenJDK 64-Bit Server VM (build 17.0.4.1+1, mixed mode)

@Munzu what is the output of java --version?

I'm currently getting the following compile error:

[INFO] Compiling 300 source files to /home/tai/.cache/paru/clone/cryptomator/src/cryptomator-1.6.15/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.702 s
[INFO] Finished at: 2022-10-09T10:21:04+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project cryptomator: Fatal error compiling: error: release version 17 not supported -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
==> ERROR: A failure occurred in build().
    Aborting...

@purejava Thanks for the hint. Just applied your suggested changes :)

Java 18 is out. Building the package on a systen with Java 18 installed, it downloads the Java 17 makedependency, but the build nevertheless fails with:

==> Beginne prepare()...
You don't have a Java 17 JDK selected but the following installed on your system:
  java-17-openjdk
Select a Java 17 JDK using "sudo archlinux-java set [name from the list above]"
If you switched to a JDK 17, please re-run the installation.
==> FEHLER: Ein Fehler geschah in prepare().
    Breche ab...

This could be improved with makedepends=('java-environment>=17' 'maven') and a modified error message. I changed the message for keepassxc-cryptomator, maybe you want to take a look.

@SailReal ok i does it