Skip to content

Conversation

@dreis2211
Copy link
Contributor

@dreis2211 dreis2211 commented Mar 28, 2017

Hey,

while working on https://jira.spring.io/browse/SPR-15395 I noticed that Spring-Boot is creating some hash codes for primitives on its own as well. So this PR replaces those with calling Spring's ObjectUtils.hashCode() variants. Seemed more consistent than using the JDK ones, but I'd be happy to use them if you tell me to.

I hope you don't mind that I changed to ObjectUtils.nullSafeEquals/hashCode() in FileSnapshot for the one none-primitive field while being on this one.

Cheers,
Christoph

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 28, 2017
@dreis2211
Copy link
Contributor Author

Having trouble to find out what checkstyle is apparently not happy with.

@wilkinsona
Copy link
Member

@dreis2211 I think I've just fixed the Checkstyle plugin's configuration so that the violations can be seen even when the build's run with -q (as it is on Travis). You could rebase on top of the latest master and then force-push to get a fresh build. Alternatively, we can take care of whatever the problem is when we come to merge this.

@dreis2211 dreis2211 closed this Mar 28, 2017
@dreis2211 dreis2211 deleted the hashcode-cleanup branch March 28, 2017 19:41
@dreis2211
Copy link
Contributor Author

Thanks @wilkinsona . As I screwed up the history a bit, I opened another clean one. Sorry for that.

@snicoll snicoll added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: duplicate A duplicate of another issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants