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
I have a build with 20+ maven modules where about a dozen contain rest controllers.
If i run with mvn clean install all is good
But we normally run the build in parallel for significant speed savings with mvn clean install -T1C
Then we hit this issue non-deterministically
if(referenceDataObject == null) {
// Investigation on a rare bug where the reference is not found.thrownewRuntimeException(
"Writing schema but could not find a reference for class " + dataObject.getJavaClass().getSimpleName());
}
I suspect the issue is in ApiResourceScanner, where a static reference to the TagLibrary gets overwritten.
Thank you @dantheperson, I think you are right. Fun fact: after almost 2 years of utilisation, someone in my company reported me this issue yesterday. 😮
This will require me a bit of work since it is not the only "not thread safe" logic.
I have a build with 20+ maven modules where about a dozen contain rest controllers.
If i run with
mvn clean install
all is goodBut we normally run the build in parallel for significant speed savings with
mvn clean install -T1C
Then we hit this issue non-deterministically
I suspect the issue is in ApiResourceScanner, where a static reference to the TagLibrary gets overwritten.
The text was updated successfully, but these errors were encountered: