-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update to checkstyle 8.19 #158
Conversation
Please note that the tabWidth setting of the active configuration is used to calculate editor annotations. On version number update, yes I always do this as part of the release process, separate from the other changes. |
Coming from here:
Ultimately originating from here: eclipse-cs/net.sf.eclipsecs.core/src/net/sf/eclipsecs/core/config/ConfigurationReader.java Line 165 in 214b6b0
|
Just to confirm, property did not move, it was added to Checker and to all FileSets. Before this change it was only in Checks and TreeWalker. See checkstyle/checkstyle@87a3357#diff-f7f32abc19eaa1b7ce3ac0595324121a . |
@rnveach In any case having tabWidth configured on potentially multiple places makes it much harder for eclipse-cs to figure out which tabWidth to use. |
Before our change, all checks could configure tabWidths differently. You could specify it in TreeWalker, and override it in each individual check making them all have different widths. So adding it to more places wasn't that much different and at the time we thought it wasn't a bad idea. When upgrading sonar plugin, this became a huge contention and long discussions. checkstyle/sonar-checkstyle#204 and checkstyle/sonar-checkstyle#209 . We were leaning to how you suggest, only 1 place to set
Can you give me a basic example so we can understand better? How are the counts different from Checkstyle and Eclipse. |
@Bananeweizen , please try to reference issue number in git commit message, it helps a lot. Commit message better to be "Issue #145: update to checkstyle 8.19" |
Yes, let's keep it for now as is, as it did not make any problems before, it is ok to keep it. We need to analyse proposed change before making it. |
Do you know what caused checkstyle all jar to basically double in size in 1 release? |
size issue was moved to checkstyle/checkstyle#6713 |
* use library 8.19 * move tabWidth from TreeWalker to Check * add AnnotationLocation values and defaults * get tabwidth from either TreeWalker or Checker (whatever first declares the attribute)
e116084
to
f6dcf54
Compare
I've modified the ConfigurationReader to take the tabWidth from the first occurrence at either Checker or TreeWalker now. Please be aware that I could not run the newly added tests locally (due my company firewall restricting the Internet access), so I will have to fix potential test failures from a private machine tomorrow. |
travis:
|
@@ -2,21 +2,21 @@ Manifest-Version: 1.0 | |||
Bundle-ManifestVersion: 2 | |||
Bundle-Name: Checkstyle Library | |||
Bundle-SymbolicName: net.sf.eclipsecs.checkstyle | |||
Bundle-Version: 8.18.0.qualifier | |||
Bundle-Version: 8.19.0.qualifier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This accidental number update causes the build to fail
@Bananeweizen , please find time to finish this PR. |
This is PR is abandoned .... |
#145
I've verified this version at runtime regarding the AnnotationLocation
changes, but I'm not sure where to verify the tabWidth changes in the
EclipseCS UI.
This is part of #145, but contains only the library upgrade, not the necessary version changes for the EclipseCS release (as Lars typically splits this into 2 commits).