ripme: Cant run version 2.1.4 with java 17

And that is specially there with my rss reader I saw that as soon java 21 also were installed then it failed right away since its posible using environment path ( and I have seen it several times just the one I remember off top of my head ) and possible that is only looks at program name in path

@tanja84dk , i checked RSSOwlnix, and it does NOT need JAVA_HOME set to build and run, see here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rssowlnix

this thing contains a bug though, as it does not set the path to java before running rssowl which makes it fail as you described.

$ cat /usr/bin/RSSOwlnix 
#!/bin/bash
export RSSOWLNIX_HOME=/usr/lib/RSSOwlnix
exec $RSSOWLNIX_HOME/RSSOwlnix "$@"

add the correct java to the PATH, and it works. you do not add it to your global path variable, only when starting something which needs an old one. same is valid to start eclispe as well, create a shell or windows cmd file and set the path to java before:

$ cat /usr/bin/RSSOwlnix 
#!/bin/bash
export PATH=/usr/lib/jvm/java-11-openjdk/bin:$PATH
export RSSOWLNIX_HOME=/usr/lib/RSSOwlnix
exec $RSSOWLNIX_HOME/RSSOwlnix "$@"

I cloned the git repo, I was able to build it and it built out a jar with filename ripme-2.1.5-4-3410a517.jar so I can now run this app again since I use Java 17 as my default now.

the version number is set by a gradle plugin: https://github.com/jgitver/gradle-jgitver-plugin, and it takes the version out of the last tag in the git repository. if you clone the repo and build it should do the trick https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository

@tanja84dk nowadays you should not set java home any more. you set the bin directory into the path maybe or you call java with its full path. on windows as well linux. when ou call java, it knows where it is installed.

I had my JAVA_HOME set to Java 11 not 17 so that’d do it lol

I was able to build it now with Java 17, however, it looks like it builds a ripme-0.0.0-NOT_A_GIT_REPOSITORY.jar which of course has a version number of 0.0.0, so I still get the update prompt every launch:

Yeah that help alot and no worries at all. I’m gonna try looking into how they set the version number this weekend to see if there is a way around that since I totally forgot that ( I’m normally using it cli based )

I finally was able to run it by just installing the Java SDK 21 now that it’s out of Beta

True that is also a possibility but unfortunately that aren’t a prober fix in a way. Like for me I have several programs there rely on Java 17 which it says are supported and if I install lets say 21 and that is set as java home then it’s breaking the other programs

I have the same issue. Java 17 is class file version 61, so this is using Java 21 instead I guess even though it says Java 17 in the changelog?

What it looks like for me then it looks like its Java 20 at this point https://javaalmanac.io/bytecode/versions/

But the worrying part there is that Java 20 is really soon EOL ( next month ) because its not a LTS as 17 is ( looks like java 17 isnt EOL before 2030 because of LTS )

So yeah looks like I guess its gonna be Java 21 ( which I cant use ) or stay on the old release ( since the java 20 is EOL next month )

EDIT: I found out that if I build it myself from https://github.com/ripmeapp2/ripme/tree/2.1.5 ( with the java 17.0.8 2023-07-18 LTS ) then it worked fine, so I guess its because the build system they use for some reason are running a newer version then they state

I have the same issue. Java 17 is class file version 61, so this is using Java 21 instead I guess even though it says Java 17 in the changelog?

I’m having a similar issue, Java 17 but 2.1.4 won’t start even though 2.1.3 does