checkstyle / checkstyle/contribution
update versions of some projects
- Dominant language
- Java
- Stars
- 57
- Forks
- 168
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
I do not remember a reason why we use exact versions in projects-to-test-on.properties
`elasticsearch|git|https://github.com/elastic/elasticsearch|v1.5.2||`
Example: https://github.com/checkstyle/contribution/blob/master/checkstyle-tester/projects-to-test-on.properties#L22
right now it causing a problem that java files that are referenced in diff reports is not that simple to find in web (requires bunch of click in github to find it), as they are gone and exists only in old version of project.
But for most of project it is better to switch to most recent version or even "master".
More and more projects switch to java8 with usage of its syntax, so using latest is better. We should use old version only to small amount of project if they used weird formatting before and it was good test area for us.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.