{"push_id":702747647,"size":4,"distinct_size":0,"ref":"refs/heads/master","head":"507c4447925bb5c9e4ae4fd011ebd22207a691ca","before":"f9732ddc0db583890ec9f40e18618f9228795ac5","commits":[{"sha":"9ada55dc6bd75059a8790193a137840ad8d20fec","author":{"email":"e8f08a372c88146d05bec7fffb27deeb3d6236da@pivotal.io","name":"Brian Clozel"},"message":"Fix NPE in GzipResourceResolver\n\nThis change fixes a NullPointerException in GzipResourceResolver, which\nassumed that calls to the `resolveResource` method were made with only\nnon-null values for request.\n\nThis is not the case for the VersionResourceResolver, which tries to\nresolve resources that aren't requested per se by the HTTP request.\n\nIssue: SPR-13149","distinct":false,"url":"https://api.github.com/repos/sdeleuze/spring-framework/commits/9ada55dc6bd75059a8790193a137840ad8d20fec"},{"sha":"4631add6cfe2537cc6bd5a442fe74a6604a62207","author":{"email":"3983f561e482e04844477d812f12209922eddb0d@pivotal.io","name":"Stephane Nicoll"},"message":"Add support for repeatable JmsListener\n\nPreviously, a method could only declare one Jms endpoint so if several\ndestinations share the exact same business logic, you'd still need one\nseparate method declaration per destination.\n\nWe now make sure that JmsListener is a repeatable annotation, introducing\nJmsListeners for pre Java8 use cases.\n\nIssue: SPR-13147","distinct":false,"url":"https://api.github.com/repos/sdeleuze/spring-framework/commits/4631add6cfe2537cc6bd5a442fe74a6604a62207"},{"sha":"04a7ed5f911deb6ed83ebc8bab04300ab58d9b60","author":{"email":"3983f561e482e04844477d812f12209922eddb0d@pivotal.io","name":"Stephane Nicoll"},"message":"Update release note for @JmsListeners","distinct":false,"url":"https://api.github.com/repos/sdeleuze/spring-framework/commits/04a7ed5f911deb6ed83ebc8bab04300ab58d9b60"},{"sha":"507c4447925bb5c9e4ae4fd011ebd22207a691ca","author":{"email":"e8b5bee66e35c0361db72ae98d0619cd426c2dbe@pivotal.io","name":"Sebastien Deleuze"},"message":"Make @ResponseBody method return type available for message converters\n\nThis commit adds canWrite() and write() methods to the\nGenericHttpMessageConverter interface. These are type aware variants\nof the methods available in HttpMessageConverter, in order to keep\nparametrized type information when serializing objects.\n\nAbstractMessageConverterMethodProcessor now calls those type aware\nmethods when the message converter implements GenericHttpMessageConverter.\n\nAbstractJackson2HttpMessageConverter and GsonHttpMessageConverter uses\nthese new methods to make @ResponseBody method return type available\nfor type resolution instead of just letting the JSON serializer trying\nto guess the type to use from the object to serialize.\n\nIssue: SPR-12811","distinct":false,"url":"https://api.github.com/repos/sdeleuze/spring-framework/commits/507c4447925bb5c9e4ae4fd011ebd22207a691ca"}]}