-
Couldn't load subscription status.
- Fork 143
The singleInstance property of maven launch4j is added #425
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! It looks good. I rebased it to pr-425, so we can also add support for this new feature in Gradle
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are both parameters mandatory? What if one of them is not specified?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm glad to provide some help. Here are the documents related to launch4j:
https://launch4j.sourceforge.net/docs.html
<singleInstance>
Optional, allow to run only a single instance of the application.
<mutexName>
Unique mutex name that will identify the application.
<windowTitle>
Optional, recognized by GUI header only. Title or title part of a window to bring up instead of running a new instance.
I conducted some tests on the Windows system and the results are as follows:
-
<mutexName> is required, if not set, it cannot be a single instance
-
<windowTitle> is optional. If it is not set or the value set is different from the application window title, the program can maintain a single instance, but it cannot be displayed to the frontend when the program is minimized
The singleInstance property of maven launch4j is added