sdedic opened a new pull request, #6552: URL: https://github.com/apache/netbeans/pull/6552
During debugging of #6525, it turned out that during the project read, the execution **sometimes** avoided the call to `setupLegacySupport` in our MavenEmebdder before invoking Maven - and when the execution finally reached e.g. `NbRepositoryModelResolver.resolveModel`, the LegacySupport was already set up by maven core - and by default for online operation. Futher calls to `setupLegacySupport` detected an existing session (from Maven) and did not create a NB-compatible setup. The PR just ensures the LegacySupport is set up prior to maven call, so it is consistent with NB needs. -- 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
