Shell Programming and Scripting

Hi everyone! I'm pretty bad at shell scripting and I am trying to create a java launcher. The idea is to store in a configuration file different paths (each for a different java version) and then, run a .sh file that would read the specified java path and execute the .jar file. This is what i have so far.

Content of file: Config.cfg

Code:

[JavaPaths] 
Java6=./jre/bin/java

Content of file: JavaLauncher.sh

Code:

#!/bin/bash
MYVAR=`awk -F= '/Java6=/ { print $2 }' Config.cfg`
echo "$MYVAR"
echo "$MYVAR -jar jarFile.jar"
$MYVAR -jar jarFile.jar

The echos are there for debugging purposes. Both files are in the same directory in which i also have the jre folder.

After executing

Code:

./JavaLauncher.sh

I get this:

Code:

./jre/bin/java
 -jar jarFile.jar
: No such file or directoryre/bin/java

This is what I am not getting:
Any help would be appreciated. Thanks in advance

The error message is reporting that re/bin/java is not a directory, not ./jre/bin/java

Use the full path in your configuration file.

I think this would be tighter as it seems a little counter intuitive to set the field separator to = then include the = in the pattern match. At least this way you are explicitly testing $1 and $2 rather than the whole of $0.

Code:

MYVAR=`awk -F= '$1 ~ /Java6/ { print $2 }' Config.cfg`
echo "$MYVAR"
echo "$MYVAR -jar jarFile.jar"
$MYVAR -jar jarFile.jar

As danmero says though, your problem is the path.

Hi. Yes, that's what it is being echoed, and I don't know why. The first 3 letters are being erased.
If i set the java path in the Config.cfg file to

Code:

/full/path/to/java/jre/bin/java

The output will be:

Code:

/full/path/to/java/jre/bin/java
 -jar jarFile.jarjre/bin/java
: No such file or directoryll/path/to/java/jre/bin/java

I think getting an answer to the first question would answer the rest

Yes, I agree. I just wanted to make sure it would work in case the path had a "Java6" inside of it. Anyway I also changed it and still had the same results.

I don't think it's the path. Even if it was, that wouldn't explain why the 2nd line echoed does not contain the variable and the 1st one does. Am I properly assigning the variable?

Hi.

I tried what you had in your original post, and there's no problem with it. (even on Solaris - where odd-awk-goings-on are known to occur!).

What shell are you using?

Are there maybe some hidden characters in your config file, or script (use the "od" utility to have a look)?

Wow. That was it! There were hidden characters on my script! Wouldn't ever think of it. Thank you all for the help!