Thanks for the feedback. I'll put in a deprecated for ResourceManagerPearWrapper...
I'll look into some kind of generalization for the runtime exception ..WHILE_WAITING_FOR_UIMA_AS. Can you say where the feature structure order changed in comparison to v2? I'm trying to keep things as much as reasonably possible the same, except if there is some kind of performance implication, etc. Cheers. -Marshall On 11/18/2018 5:26 PM, Richard Eckart de Castilho wrote: > Built from sources using Java 11: ok > Build uimaFIT v3 against RC: ok > Build DKPro Core (v3 version) against rc and uimaFIT v3: pretty ok > - looks like feature structure order may have changed in comparison to v2 > for cases where a stable order couldn't be expected in the first place. > > Spot checking source changes: > - ResourceManagerPearWrapper has a comment that it is no longer used but > was not marked as deprecated > - UimaRuntimeException has a > CAS_RELEASE_NOT_ALLOWED_WHILE_WAITING_FOR_UIMA_AS. > I think it would be better to have a general concept of release locking > not tied to UIMA AS - i.e. UIMA AS not being mentioned in UIMAJ-Core code. > > Looks good. > > [X] +1 OK to release > > -- Richard > >
