-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux executable doesn't start if under a path with spaces #214
Comments
Hi @salmonb! Please, can you share here the generated Thanks! |
hi @fvarrui Here is the content of startup.sh
If I run this script under a path with a space (ex: /home/bruno/dev/javapackager\ issue/... <= there is a space between javapackager and issue), then I'm getting this error:
|
Yes, thank you! I'm working on it ... I've just reproduced your issue and find out that the problem is in this line: SCRIPTPATH=$(dirname $(readlink -e "$0")) Just adding doublequotes and the problem is fixed: SCRIPTPATH=$(dirname "$(readlink -e "$0")")
I've just released the change in issue-214 branch ... please, try it and give me some feedback. I'd like to include this fix in v1.6.7. |
AppImage generation feature is already included ... as you are trying on Linux, would you mind trying the |
Great, glad that you found a fix 😃 I'm happy to test, but not sure how, as I never used a Maven plugin other than by listing it on my pom.xml... I cloned your repository and checked out the issue-214 branch, but how can I tell Maven to use it now? |
Hi @salmonb! You can build JavaPackager on your own by running next commands: git clone https://github.com/fvarrui/JavaPackager --branch issue-214
cd JavaPackager
./gradlew publishToMavenLocal Last command will install the plugin in your local repo (inside
|
hi @fvarrui Thank you, I managed to test your SNAPSHOT version by following your instructions 👍 I confirm that the Linux executable now starts correctly, good job! 😄 For the AppImage generation, some lines are logged as [ERROR] while they seem to be just [INFO], is it normal?
In the end the WebFXExample.AppImage executable file is generated.
Is it a normal requirement to install FUSE to execute AppImages? |
Yes, are you testing on WSL? Because I got same error. I've tried on LinuxMint and it seems to be working fine. 🤷♂️ Here you can find instructions and why AppImage uses FUSE. |
Branch issue-214 merged into devel. |
No, I'm on Ubuntu 22.04. FUSE is already installed but it's FUSE 3, and the AppImage requires FUSE 2. It's possible to install FUSE 2 beside FUSE 3, which I did, and then the AppImage is running 👍 Do you know if there could be an option to choose the FUSE version when generating the AppImage?
Great job 🥳 |
JavaPackager v1.6.7 released to Maven Central. See changes here. |
I'm submitting a…
Short description of the issue/suggestion:
If the path to the repository contains spaces, the Linux executable generated by Javapackager doesn't start.
Steps to reproduce the issue/enhancement:
mkdir My\ Projects
)What is the expected behavior?
The executable should run, whether or not there are spaces in the path
What is the current behavior?
The executable fails to run when there are spaces in the path
Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?
What is the motivation / use case for changing the behavior?
Just make it works :)
Please tell us about your environment:
Other information (e.g. related issues, suggestions how to fix, links for us to have context)
The text was updated successfully, but these errors were encountered: