Lazy init SMO backend and increase timeout #7587
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So I noticed since #7569 this exception when NB is started and closed before the maven indexer is initialized:
I am not completely sure why this happens. The gson wrapper can be found just fine when
NexusRepositoryIndexerImpl
is initialized normally, but when it is loaded from for the first timenetbeans/java/maven.indexer/src/org/netbeans/modules/maven/indexer/OnStop.java
Lines 48 to 52 in 1b31400
it causes the exception. Lazy loading SMO fixes it.