Update eclipse plugin to NOT create ".checkstyle" file.
All works and without this file, but this file become a problem when configuration is used as global from Eclipse, from External file. And sources are shared in team by any VCS.
We store configuration file on SVN close to sources.
Any developer start to use Checkstyle. New-by open Eclipse, install plugin, put existed config to Preferences with name "NAME1", open project, open project Properties, activate checkstyle. Done.
3.In files we have changes in ".project" and ".checkstyle".
".project" - CheckstyleNature is appear and project already become compliant to Checkstyle
".checkstyle" - store specific to project settings, but user do NOT specified them - he only activated Company Code Standart that is shared in SVN and mandatory to use.
4.Developer do commit of all changes and ".checkstyle" too.
5.Next day other developer download this project and open it (presume it already have chackstyle installed and configured with name "NAME2") - there will be a problem as ".checkstyle" demand "NAME1" config and this developer have the same config by with slightly different name.
Detected: problem with reusing
Workaround: as all developers use the same config - remove ".checkstyle" from SVN and Plugin will use global/active config.
Configure Plugin ones, open any project, ChecksttyleNature in ".project" is enough to work.
Expected: any of
Do not create ".checkstyle" file untill user specify custom settings.
Option to forbid custom settings for checkstyle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not quite sure what you are proposing here. The .checkstyle file stores project specific settings - do you propose to move them elsewehere?
thanks for answer, and sorry for my delay.
We have a minor problem with using plugin:
We store configuration file on SVN close to sources.
Any developer start to use Checkstyle. New-by open Eclipse, install plugin, put existed config to Preferences with name "NAME1", open project, open project Properties, activate checkstyle. Done.
3.In files we have changes in ".project" and ".checkstyle".
".project" - CheckstyleNature is appear and project already become compliant to Checkstyle
".checkstyle" - store specific to project settings, but user do NOT specified them - he only activated Company Code Standart that is shared in SVN and mandatory to use.
4.Developer do commit of all changes and ".checkstyle" too.
5.Next day other developer download this project and open it (presume it already have chackstyle installed and configured with name "NAME2") - there will be a problem as ".checkstyle" demand "NAME1" config and this developer have the same config by with slightly different name.
Detected: problem with reusing
Workaround: as all developers use the same config - remove ".checkstyle" from SVN and Plugin will use global/active config.
Configure Plugin ones, open any project, ChecksttyleNature in ".project" is enough to work.
Expected: any of