Skip to content
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

Closed
kwesterfeld2 opened this issue Apr 17, 2018 · 7 comments
Closed

Comments

@kwesterfeld2
Copy link

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.

@lukaszlenart
Copy link
Collaborator

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.

@lukaszlenart
Copy link
Collaborator

Could you test 1.7.22-SNAPSHOT? I have added a parallelExecution flag that will allow to run only one instance of the plugin in the given time. This should resolve the issue with blocking on resources.

@lukaszlenart
Copy link
Collaborator

See #73

@lukaszlenart
Copy link
Collaborator

PR got merged, I will prepare a new release soon

@kwesterfeld2
Copy link
Author

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:

[INFO] ------------------------------------------------------------------------
[WARNING] *****************************************************************
[WARNING] * Your build is requesting parallel execution, but project      *
[WARNING] * contains the following plugin(s) that have goals not marked   *
[WARNING] * as @threadSafe to support parallel building.                  *
[WARNING] * While this /may/ work fine, please look for plugin updates    *
[WARNING] * and/or request plugins be made thread-safe.                   *
[WARNING] * If reporting an issue, report it against the plugin in        *
[WARNING] * question, not against maven-core                              *
[WARNING] *****************************************************************
[WARNING] The following plugins are not marked @threadSafe in Yellowbrick - Tools:
[WARNING] com.akathist.maven.plugins.launch4j:launch4j-maven-plugin:1.7.23
[WARNING] Enable debug to see more precisely which goals are not marked @threadSafe.
[WARNING] *****************************************************************

@lukaszlenart
Copy link
Collaborator

1.7.24 is under way to the Central, please check and report back, thanks :)

@kwesterfeld2
Copy link
Author

kwesterfeld2 commented Oct 26, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants