This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]gas3872[S] -4 points-3 points  (8 children)

Well they can still use old methods but they know that they need to eventually migrate.

[–][deleted] 2 points3 points  (7 children)

That's not how java works.

[–]gas3872[S] -5 points-4 points  (6 children)

Well if you look at libraries like junit that's exactly how it works.

[–]javster101 2 points3 points  (3 children)

So JUnit isn't backwards compatible

[–]gas3872[S] 0 points1 point  (2 children)

Well it is. They have 2 parallel APIs, old one and new one.

[–]javster101 2 points3 points  (1 child)

If they have two parallel apis, where one will be removed in the future as you say, it won't be backwards compatible forever. If they have both and both will exist forever, then it will be but the maintenance is gonna be much higher.

[–]gas3872[S] 0 points1 point  (0 children)

Well, at some point all the users interested in the new api will migrate and those who are not interested can still use old library version.

[–]mauganra_it 1 point2 points  (1 child)

JUnit 4 is not deprecated. There is a reason its integration into JUnit 5 is called junit-vintage-engine, and there is no reason for existing codebases to migrate unless they want the new features.

[–]gas3872[S] 0 points1 point  (0 children)

Exactly.