Rename junit4-launcher-runner to junit4-runner

[junit-team]

Rename junit4-launcher-runner to junit4-runner

[marcphilipp]

What should the package org.junit.gen5.junit4runner be called then?

[sbrannen]

How about org.junit.gen5.junit4.runner?

If we go that route, I'm very tempted to rename org.junit.gen5.engine.junit4 to org.junit.gen5.junit4.engine for consistency, resulting in:

• org.junit.gen5.junit4.runner
• org.junit.gen5.junit4.engine

I realize the latter would then be inconsistent with org.junit.gen5.engine.junit5, but I could live with that.

Thoughts?

[jlink]

Org.junit.gen5.junit5on4

It's a temporary thing anyway, so doesn't matter much IMO.

Am 02.01.2016 um 19:25 schrieb Marc Philipp [email protected]:

What should the package org.junit.gen5.junit4runner be called then?

—
Reply to this email directly or view it on GitHub.

[jlink]

I'd prefer engine in front. The JUnit 5 on 4 runner will go away anyway.

Am 02.01.2016 um 20:10 schrieb Sam Brannen [email protected]:

How about org.junit.gen5.junit4.runner?

If we go that route, I'm very tempted to rename org.junit.gen5.engine.junit4 to org.junit.gen5.junit4.engine for consistency.

I realize that would then be inconsistent with org.junit.gen5.engine.junit5, but I could live with that.

Thoughts?

—
Reply to this email directly or view it on GitHub.

[marcphilipp]

Team Decision: org.junit.gen5.junit4.runner

[sbrannen]

👍

[sbrannen]

FYI: I split up the orginial TODO into 4 TODOs.

[sbrannen]

Resolving this issue.

See related commits for details.

[marcphilipp]

👍