Not always predictable (you expect no more than 99 versions and finally have).
Can be against conventions. Le 2 octobre 2015 13:07:15 GMT+02:00, David kerber <dcker...@verizon.net> a écrit : >On 10/2/2015 4:33 AM, l.pe...@senat.fr wrote: >> Hi. >> >> I am using parallel deployment to upgrade my webapps with no >downtime. >> >> I just have a small issue / question on how the latest version is >selected. >> >> As far as I understand, the container select the latest version by >> lexicographically ordering the version string. >> >> So if >> >> webapp##1.0.51 >> >> and >> >> webapp##1.0.52 >> >> are deployed version 1.0.52 will be selected. >> >> I just have a periodic issue with versions ranging from 1.0.1, >> 1.0.2,...1.0.9 and then jumping to 1.0.10 (same thing for hundreds of >> course) : 1.0.9 is prefered to 1.0.10 because 9 is after 1. >> >> Is there a way to configure tomcat so that it analyses the version >part >> as a triplet of numbers ? And so understand that 10 is more recent >than 9 ? > >Why not format your versions differently, to see 1.0.09? > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. | | AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT. |
