apim-cli.sh not working when JAVA_HOME doesn't exist about apim-cli HOT 5 CLOSED

Hi @lacg, Thanks for the feedback!

I assume you have not downloaded the latest release, but instead cloned the project and called the script like so:

[axway@api-env apim-cli]$ ./modules/apim-cli/assembly/scripts/apim.sh
/usr/bin/java

Error: Could not find or load main class com.axway.apim.cli.APIManagerCLI

Please download the latest release package from here: https://github.com/Axway-API-Management-Plus/apim-cli/releases I have tested this with a fresh installation and it's working as expected.

from apim-cli.

Hi @cwiechmann, I downloaded from here and it says latest release. Though, I can double check tomorrow morning...
Thanks, Luiz

from apim-cli.

Hmm, perhaps you have downloaded the source-release-package instead of the distribution package. I'm waiting for your feedback.

from apim-cli.

Yeah, I downloaded the 1.2.1 latest release!
I had cloned earlier on, but I couldn't make it work and I realized it was not the right way (and the folder was not easy to find (/modules/apim-cli/assembly/scripts/). Thus I used the tar file for the Mac and the Zip file for the Windows and both have the 1.2.1 name on the folder with /scripts on the subfolder, so it is not the wrong version and the wrong script.
Don't get me wrong, if JAVA_HOME is well defined, it should work just fine. If no JAVA_HOME is defined, it was also supposed to work and I have no idea why it is not on Windows (on Linux/Mac, it will depend on how the OS treats the relative path/working directory). I had issues before with certain versions of bash/zsh not changing the working directory with cd .. (most does though)
To solve this, or we could change the pwd variable manually (there is no perfect way on doing this 100% of the time on all shells) or use absolute paths (a problem with longer paths and class paths character limits). In the end, no solution will be perfect... :( As the jar files are not that much, I went with the absolute path... but that is no way THE only solution.

from apim-cli.

Based on my understanding I think it's okay to close this issue. Let me know, if there is anything else I can do.

from apim-cli.