You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you import projects, a didChangeConfiguration request triggers Java Runtime changes, that in turn triggers a full rebuild of the workspace.
I think we could improve the situation in BaseInitHandler.initialize, where we could do something like:
if (initializationOptions.get(SETTINGS_KEY) instanceofMap) {
Objectsettings = initializationOptions.get(SETTINGS_KEY);
@SuppressWarnings("unchecked")
Preferencesprefs = Preferences.createFrom((Map<String, Object>) settings);
prefs.setRootPaths(rootPaths);
preferenceManager.update(prefs);
if (firstTimeWorkspaceIsOpened) {
// We don't care about triggering a full build here, like in onDidChangeConfigurationtry {
JVMConfigurator.configureJVMs(prefs);
} catch (CoreExceptione) {
logException("Failed to configure Java Runtimes", e);
}
}
logInfo("Updated preferences from initialization options");
}
The text was updated successfully, but these errors were encountered:
When you import projects, a didChangeConfiguration request triggers Java Runtime changes, that in turn triggers a full rebuild of the workspace.
I think we could improve the situation in BaseInitHandler.initialize, where we could do something like:
The text was updated successfully, but these errors were encountered: