Thanks Richard, The workaround seems to do the trick, and I agree with your choice to fix this (left a comment). Most of our pipeline seems to work with UIMA 3 now, but there are some issues left unrelated to this, so I might be back with other questions in the near future.
Cheers Mario On 4 Apr 2020, at 18:57 , Richard Eckart de Castilho <[email protected]> wrote: Hi Mario, On 29. Mar 2020, at 15:13, Mario Juric <[email protected]> wrote: Done. Sorry for not obeying to the guidelines at this point, since I am not sure it’s a real issue or whether it’s me that has been doing something wrong all along, and it just happens to fail now. I expect you just need this initially to verify the issue and then we can do a proper PR later. Short story - there is a bug and there is a workaround (based on your PR): cast the aggregate description to ResourceSpecifier: bindResource((ResourceSpecifier) aggregateDescription, DummyResource.RESOURCE_KEY, createSharedResourceDescription("", DummyResource.class)); Long story ... *sigh* ... we have another signature clash - that's what I hoped to have fixed going from uimaFIT v2 to v3... but while fixing one, I unfortunately introduced another one. Here is the whole shebang: https://issues.apache.org/jira/browse/UIMA-6214 If you have a moment, maybe you can have a look at the issue and give a comment whether you agree with my choice of how to fix the issue. Cheers, -- Richard ________________________________ Disclaimer: This email and any files transmitted with it are confidential and directed solely for the use of the intended addressee or addressees and may contain information that is legally privileged, confidential, and exempt from disclosure. If you have received this email in error, please notify the sender by telephone, fax, or return email and immediately delete this email and any files transmitted along with it. Unintended recipients are not authorized to disclose, disseminate, distribute, copy or take any action in reliance on information contained in this email and/or any files attached thereto, in any manner other than to notify the sender; any unauthorized use is subject to legal prosecution.
