I remember munging around in Junit3 -> Junit4 conversion. It was not at all pretty. There are some constructs we use that do not map easily (dynamicly generated test suites comes to mind). But I agree we should migrate.
On Thu, Jun 28, 2018 at 3:11 PM, A. Soroka (JIRA) <j...@apache.org> wrote: > > [ https://issues.apache.org/jira/browse/JENA-1568?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16526333#comment-16526333 ] > > A. Soroka commented on JENA-1568: > --------------------------------- > > [~andy.seaborne], is this an example of a larger program of migration we'd > like to make? JUnit5 is out, and while I'm _not_ suggesting we tangle with > that now, it might be nice to uniformly use 4. > > > Don't use JUnit3 TestCase for in SSE tests > > ------------------------------------------- > > > > Key: JENA-1568 > > URL: https://issues.apache.org/jira/browse/JENA-1568 > > Project: Apache Jena > > Issue Type: Improvement > > Affects Versions: Jena 3.8.0 > > Reporter: Andy Seaborne > > Assignee: Andy Seaborne > > Priority: Minor > > Fix For: Jena 3.9.0 > > > > > > Follows on from JENA-1566. > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
