| Git Clone URL: | https://aur.archlinux.org/jameica.git (read-only, click to copy) |
|---|---|
| Package Base: | jameica |
| Description: | free runtime environment for java applications |
| Upstream URL: | https://www.willuhn.de/products/jameica/ |
| Licenses: | GPL2 |
| Submitter: | jakob |
| Maintainer: | fordprefect |
| Last Packager: | fordprefect |
| Votes: | 88 |
| Popularity: | 0.27 |
| First Submitted: | 2006-10-21 16:11 (UTC) |
| Last Updated: | 2024-09-14 08:52 (UTC) |
Also, in order to make jameica use java8 on systems where it is installed, you could patch the starter like so:
if [ -d /usr/lib/jvm/java-8-openjdk/bin/ ]; then export PATH=/usr/lib/jvm/java-8-openjdk/jre/bin/:$PATH fi
That would help people who usually use a newer java version but would still like to also use mashup (which is still stuck at java 8).
Just a nitpick/heads-up: According to the author of mashup, java-jce_ustrength is no longer required since Java 8.u161. See: https://hibiscus-mashup.derrichter.de/index.php/faq?id=94:unlimited-strength-java&catid=94
@stepborc: please import the key and try again: gpg --receive-keys 5A8ED9CFC0DB6C70. You can setup gpg autoretrieve as well.
@mareex: jre versions are a mess. jre above 9 includes java-jce_ustrength, which otherwise needs to be supplied as dependency. However, some jameica plugins (notably mashup) require the oracle java in version 8 (still the suggested version at their website). so, i agree that enforcing java-environment>10 does not really make sense, the fractured java ecosystem is not easy to handle in this case.
Unfortunately there is a problem with the public key.
"FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 5A8ED9CFC0DB6C70)"
Any valid reason why this PKGBUILD enforces 'java-runtime>=10'? Everything works fine here with java 8
@fordprefect: Works on my side. Thanks
Ok. I will leave this as it is now and fix this tonight on my arch machine. Sorry! EDIT: should all be fixed now, runs like this smoothly at least for me. Please test and report issues. Thanks everyone!
@fordprefect: Running sed -i 's/jameica-linux/\/opt\/jameica\/jameica-linux/g' /usr/bin/jameica and running jameica afterwards returns an error saying manifest /usr/bin/plugin.xml not readable.
I guess it is because the current path is incorrect (like @Taijian already stated)
@Taijian: damn, didn't think about that. Unfortunately I'm not at my machine now, so I can't test. Does it work prepending the jameica-linux with /opt/jameica in /usr/bin/jameica:21 ?
OK, now it doesn't start any more. Looking at the patch you removed, I think you went a little too far. You should only have removed the java9 compatability line, NOT the whole patch, because now /usr/bin/jameica looks for jameica-linux64.jar in whatever dir the user was in when trying to start jameica, not in /opt/jameica. So please restore most of 'jameica-start-script.patch', only removing the java9 part.
Thank you!
Pinned Comments
fordprefect commented on 2020-03-06 08:28 (UTC) (edited on 2022-05-10 09:33 (UTC) by fordprefect)
In case of unknown PGP key run
gpg --receive-keys 5A8ED9CFC0DB6C70Due to widespread keyserver rot the use of
keys.openpgp.orgis encouraged, e.g. by addingkeyserver keys.openpgp.orgto your~/.gnupg/gpg.conf.