-
Notifications
You must be signed in to change notification settings - Fork 463
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
[WFCORE-625] Error message in CLI if extension existing on the server is not present in the CLI installation #632
Conversation
…tension existing on the server is not present in the CLI instalaltion
Windows Build 1212 is now running using a merge of d1400db |
Linux Build 1560 is now running using a merge of d1400db |
…until the server is completely started
d1400db
to
1a4aaf9
Compare
Linux Build 1560 outcome was SUCCESS using a merge of 1a4aaf9 |
Windows Build 1212 outcome was SUCCESS using a merge of 1a4aaf9 |
Windows Build 1214 is now running using a merge of 1a4aaf9 |
Linux Build 1561 is now running using a merge of 1a4aaf9 |
Linux Build 1561 outcome was SUCCESS using a merge of 1a4aaf9 |
Windows Build 1214 outcome was SUCCESS using a merge of 1a4aaf9 |
Core - Full Integration Build 815 outcome was FAILURE using a merge of 1a4aaf9 Build problems:Failed tests detected Failed tests
|
[WFCORE-625] Error message in CLI if extension existing on the server is not present in the CLI installation
[JBEAP-15999] FileSystemDeploymentService#handleNotification() can cr…
This supercedes #599 with an additional fix to resolve a problem with the CLI embedded server that testing of 599 revealed.