sdedic opened a new pull request, #8694: URL: https://github.com/apache/netbeans/pull/8694
During investigation of #8681, it turned out that during the test execution Maven build is **run twice in parallel over the same project directory**. Maven itself does not lock out itself in such case and one maven will hapilly delete or update a JAR while another maven tries to use it or generate classes while other maven tries to read them - leading to all kinds of mysterious errors, as I've noted in comments to #8681. This bug is also 'reachable' by users of VSNetbeans extension: just try to Debug the applicaiton before the priming build completes. In most cases the parallel builds won't interefere that much, but in an unlucky case one of them or both fail with various errors. This PR changes behaviour of DAP protocol implementation in NetBeans Language Server so that if a Language Server start is also requested, then the DAP will wait until the initial LS project open (that includes possible priming builds of the initial projects) finish (not necessarily succesfully). DAP client (vscode) always wait for the DAP initialization to complete, so it will be forced to wait until the project primes, then the application will be started through the build system. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
