Lars Koedderitzsch

Sorry for the late reply, premises here @SF are largely vacated. The project moved to Github https://github.com/checkstyle/eclipse-cs for project services (Git, Issues) and Bintray for binary downloads. Update site archives starting from version 8.7.0 can be found here: https://bintray.com/eclipse-cs/eclipse-cs/update-site-archive#files/update-site-archive

@Ashis please attach your checkstyle configuration file

FYI the move of eclipse-cs sources to Github as a first measure is a go, see https://github.com/checkstyle/eclipse-cs Thanks to @Bananeweizen for suggesting and to @Roman for taking it under the wings of the Checkstyle organisation at Github

I imagine sevntu metadata is maintained alongside the checks, so whenever you change something (add a property, new check etc.) you will update the eclipse-cs metadata accordingly? For eclipse-cs this is not the case. Instead once in a while I need to check all changes in Checkstyle for their relevance to the metadata. For example: a new check is added a check gets a new property an existing property is changed - for instance changes to allowed or default tokens addition of new message keys * or...

@Roman - thanks and agreed, hosting eclipse-cs sources under the Checkstyle organisation in Github would be the best course. I'll send you a private message shortly. @Richard - interesting, although I am unsure how this can help with eclipse-cs metadata maintenance. As I understand I would still need to meticulously check all changes in a Checkstyle release, whether they have any relevance for the metadata. Ideally Checkstyle itself would expose this metadata (e.g. via annotations) to integration...

Hey Eric. There is effort required for actually updating the plugin to the latest Checkstyle version. Most of the time the bulk of work is hunting down Checkstyle changes which require metadata changes using the Checkstyle release notes. The build itself is automated via Maven/Tycho, however, getting a release out is a multi-stepped, non-automated process. For instance updating the plugin from 8.0 to 8.5 took me about a day of work for updating and releasing. If I had updated to all intermediary...

Oh, how did that slip through... Fixed now and new version 8.5.1 made available.

Configuration via dialog no longer possible with version 8.5