Niklas Rentz

This issue is migrated from the old KIELER Pragmatics JIRA issue tracker. See the old discussion on this ticket in [KIPRA-1845](https://rtsys.informatik.uni-kiel.de/jira/projects/KIPRA/issues/KIPRA-1845).

This issue is migrated from the old KIELER Pragmatics JIRA issue tracker. See the old discussion on this ticket in [KIPRA-1492](https://rtsys.informatik.uni-kiel.de/jira/projects/KIPRA/issues/KIPRA-1492).

I also had that option in mind, but I think the configurability on the Sprotty side leads to better maintainability on projects that want different behavior, such as our project....

It seems like this is not a problem with this PR, but with the main branch in general - that Itemis site that is used by every build does seem...

See the discussion over at the xtext repository: eclipse-xtext/xtext#3443 The issue seems to be resolved for now, the file can be downloaded again. KIELER does not rebuild its grammar every...

If we are to remove Guava, KLighD will deprecate the current API first, eventually removing it probably during a major version update. I try to keep semantic versioning a thing,...

Generally I like the idea of reducing the amount of dependencies, especially as they are not needed anymore with newer versions of Java. I would like to merge this (and...

> Of course. I just want to mention that Java-11 is already required and the generated byte-code probably already targets Java-11 JVMs. And since the project is configured to build...

Thanks again @HannesWell! Sorry for the delay, holiday and a conference also hindered me in looking into this earlier. Now I got a little more time to look at this...

> Almost any change in the method signature (except changing parameter names) is a binary incompatible change, even changing the return type in a source compatible way: > > *...