Order of attributes significant in zipfileset?

I discovered this in ant 1.6.5, and found that it still behaves this way in 1.9.7. If you have a element with both a dir and a file attribute, it will produce different results depending on the order in which those attributes appear. If the file attribute appears first, it behaves as you would

Re: Order of attributes significant in zipfileset?

From: "Caldarale, Charles R" <chuck.caldar...@unisys.com> To: Tomcat Users List <users@tomcat.apache.org>; Dave Glasser <dglas...@pobox.com> Sent: Tuesday, April 26, 2016 2:32 PM Subject: RE: Order of attributes significant in zipfileset? >>

Re: OT: Re: Order of attributes significant in zipfileset?

Good to know! Thanks George! From: George Sexton To: Tomcat Users List Sent: Tuesday, April 26, 2016 4:06 PM Subject: OT: Re: Order of attributes significant in zipfileset? This isn't as bad as the delete task. If you specify dir

Re: jsessionid path parameter: Is this compliant with the Servlet 3.0 spec?

Thanks, that is pretty clear and unambiguous, as is "The name of the parameter must be jsessionid." When the spec is in conflict with itself, I'm happy to consider Tomcat the reference implementation. The reason a session cookie name had to be specified in the first place was because we

jsessionid path parameter: Is this compliant with the Servlet 3.0 spec?

This text is based on a stackoverflow question I posted earlier today: https://stackoverflow.com/questions/48600576/jsessionid-as-path-parameter-not-working-in-tomcat/48602272 I'm using Tomcat 7.0.84, and my web app uses the Servlet 3.0 deployment descriptor. The web.xml file contains this: