F5F Stay Refreshed Software Operating Systems Issue with pop_os.jar loading or execution

Issue with pop_os.jar loading or execution

Issue with pop_os.jar loading or execution

D
davidspyro
Member
213
11-28-2016, 12:26 PM
#1
While attempting to launch a .jar file, it opens into the Archive Manager instead of the Java Runtime Environment. When using other applications, it disappears from view. I confirmed enabling "Allow executing file as program." Despite installing Java via both Terminal and Synaptic Package Manager, the problem persists. After the latest Java installation via Terminal, I read about potential configuration steps, though details remain unclear.
D
davidspyro
11-28-2016, 12:26 PM #1

While attempting to launch a .jar file, it opens into the Archive Manager instead of the Java Runtime Environment. When using other applications, it disappears from view. I confirmed enabling "Allow executing file as program." Despite installing Java via both Terminal and Synaptic Package Manager, the problem persists. After the latest Java installation via Terminal, I read about potential configuration steps, though details remain unclear.

S
Sunahh
Posting Freak
863
12-13-2016, 02:32 PM
#2
Executing the JAR file via the command line is possible.
S
Sunahh
12-13-2016, 02:32 PM #2

Executing the JAR file via the command line is possible.

M
McAlden
Member
60
12-15-2016, 10:22 AM
#3
This command runs a JAR file using Java. Navigate to the directory with the jar, then execute it with the specified path. Make sure Java is installed and accessible in your system's PATH.
M
McAlden
12-15-2016, 10:22 AM #3

This command runs a JAR file using Java. Navigate to the directory with the jar, then execute it with the specified path. Make sure Java is installed and accessible in your system's PATH.

T
taconiebre
Senior Member
506
12-15-2016, 02:28 PM
#4
Launch terminal, move to the directory containing your JAR, then execute "java -jar [filename].jar". Some JARs aren't directly runable on the system and require this approach.
T
taconiebre
12-15-2016, 02:28 PM #4

Launch terminal, move to the directory containing your JAR, then execute "java -jar [filename].jar". Some JARs aren't directly runable on the system and require this approach.

M
MrCupquake
Member
229
12-16-2016, 08:46 AM
#5
It functioned correctly, thanks for your assistance. The reason my member tag shows as empty is unclear.
M
MrCupquake
12-16-2016, 08:46 AM #5

It functioned correctly, thanks for your assistance. The reason my member tag shows as empty is unclear.

D
DDotty2
Member
223
12-16-2016, 03:00 PM
#6
I invested a lot of time trying to understand this.
D
DDotty2
12-16-2016, 03:00 PM #6

I invested a lot of time trying to understand this.

M
McJoelPlayz
Member
65
12-29-2016, 09:27 AM
#7
a jar is not executable—it's merely an archive. When using Java, opening it via the standard dialog sends the filename directly to the binary, which doesn't function correctly because Java requires a class name with extra parameters. To fix this, set the -jar option properly: java -jar %1. If it's not configured right, you won't be able to run the jar by double-clicking. The simplest solution is to ask the developer for guidance on launching the distributed app. You can run it simply as "java -jar %1," or more complexly with additional parameters. Another option is requesting a proper start script instead of relying on user input. If the project lacks one, it might just be provided out of curiosity—what you try to do anyway?
M
McJoelPlayz
12-29-2016, 09:27 AM #7

a jar is not executable—it's merely an archive. When using Java, opening it via the standard dialog sends the filename directly to the binary, which doesn't function correctly because Java requires a class name with extra parameters. To fix this, set the -jar option properly: java -jar %1. If it's not configured right, you won't be able to run the jar by double-clicking. The simplest solution is to ask the developer for guidance on launching the distributed app. You can run it simply as "java -jar %1," or more complexly with additional parameters. Another option is requesting a proper start script instead of relying on user input. If the project lacks one, it might just be provided out of curiosity—what you try to do anyway?