-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Using -T NNN with maven build can cause launch4j plugin to fail #72
Comments
I am not sure if this is possible, I meant the only option I see is a lock file that will allow one execution of the plugin in given time. |
Could you test 1.7.22-SNAPSHOT? I have added a |
See #73 |
PR got merged, I will prepare a new release soon |
Sorry, just now getting back to this. I am using the latest launch4j version (1.7.23) and added the parallelExecution flag, but Maven still gripes:
|
1.7.24 is under way to the Central, please check and report back, thanks :) |
Thanks !
On Oct 26, 2018, at 12:02 PM, Lukasz Lenart <[email protected]<mailto:[email protected]>> wrote:
1.7.24 is under way to the Central, please check and report back, thanks :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#72 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AkXsIj4o0BMk8J_Gxy9slMTmarajRXzeks5uozIggaJpZM4TYtkI>.
|
Using parallel execution for a multi-module project that generates multiple .exe using launch4j fails randomly. This is because the launch4j plugin is not thread-safe. It would be great if there was some synchronization put in place to prevent clobbering the execution of multiple simultaneous modules generating .exe.
The text was updated successfully, but these errors were encountered: