no worries - I'm doing the compatibility testing myself :-) (it's somewhat less embarrassing that way) I just finished testing uimaFIT - found some issues and fixed most of them. The good news is that v3 runs the tests faster than v2 ...
My technique: I use the migration tool (being incrementally improved as I have to use it...) to convert any JCas classes, then I change the pom to specify Java 8, and make it depend on uima 3.0 (as necessary), then run the various project/src/test/java JUnit tests. Then fix what problems arise, and iterate ... -Marshall On 12/21/2016 10:06 AM, Peter Klügl (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767260#comment-15767260 > ] > > Peter Klügl commented on UIMA-5225: > ----------------------------------- > > It's still on my TODO list to run ruta against v3 but I have not found the > time yet. > >> uv3 backward compatibility work >> ------------------------------- >> >> Key: UIMA-5225 >> URL: https://issues.apache.org/jira/browse/UIMA-5225 >> Project: UIMA >> Issue Type: Improvement >> Components: Core Java Framework >> Reporter: Marshall Schor >> Assignee: Marshall Schor >> Priority: Minor >> Fix For: 3.0.0SDKexp >> >> >> Try uv3 with other big frameworks (uimaFIT, Ruta, uima-as, ducc, add-ons), >> find / fix backward compatibility issues. Also temporarily set the semver >> backwards compatibility level to catch things, and review them. > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
