Hi Rossen, Thanks for bringing this ticket to our attention. I must mention that I like Michael's input, even if I didn't have time to review his contribution to the apache dev list yet.
I'll remove the dependency on tiles-request-servlet-wildcard in tiles-request 1.1 / tiles 3.1 (actually I'd like to deprecate tiles-request-servlet-wildcard entirely, we'll have better options in tiles 3.1 imho). I'll also upgrade all dependencies to spring 3.2, since I believe spring 3.2 will be out before tiles 3.1. Actually I think it would be a good idea to make a new release of tiles 3.0/request 1.0 with the upgraded dependency (and svnpubsub, which is an Apache requirement for the end of this year). Is spring 3.2 GA still happening 10 days from now? Regards, Nick PS: I'm cc-ing this to the Apache dev mailing list for eventual further discussion. On 12-11-29 09:37 AM, Rossen Stoyanchev wrote: > Hi, > > Just a quick note on this ticket: > https://jira.springsource.org/browse/SPR-10054 > > The "tiles-request-servlet-wildcard" dependency brings in spring-web version > 2.5.6 and causes issues if the application already depends on a different > version of spring-web transitively. On my end I intend to drop the need for > "tiles-request-servlet-wildcard". It provides only one short class, which we > can include with our own integration. > > I'm not sure whether it makes sense for you to consider some changes on your > end since the need for spring-web in "tiles-request-servlet-wildcard" is very > small. > > Regards, > Rossen >
