You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are we considering adding any of those? I'd gladly help with asking for permission from the original author, if needed, and integrating the cleaned-up code into JDT if that helps in any way.
The text was updated successfully, but these errors were encountered:
What contribution is welcome and where do you prefer it to be kept separate? In fact I was thinking about contributing a cleanup to migrate junit 4 to junit 5. definitly this is junit specific. On the other side there is already a lot of junit specific code in jdt and jdts test itself are based on junit too.
See carstenartur/sandbox#110
Good question, I'd say java specific thinks belong to the scope of JDT.UI. JUnit does not, but is interesting for the eclipse ide as a whole. I actually would try to use it to convert SWT to junit 5. The problem i see is that as the codebase grows it is hard to maintain. Often edge cases remain unsolved which gives a bad light on jdt.
Imho the strong connection of junit and Eclipse is a strength and has a reason: Erich Gamma, famous member of the gang of four and involved in the early days of Eclipse and JUnit at the same time.
The original code mining repo, https://github.com/angelozerr/jdt-codemining, has a few more tricks than the current JDT. Namely,
var
local inference type, https://github.com/angelozerr/jdt-codemining/tree/master/org.eclipse.jdt.codemining/src/org/eclipse/jdt/experimental/ui/javaeditor/codemining/var, already requested by [code mining] show inferred type for local "var" statements #329)Are we considering adding any of those? I'd gladly help with asking for permission from the original author, if needed, and integrating the cleaned-up code into JDT if that helps in any way.
The text was updated successfully, but these errors were encountered: