TTL not applied when using resolver attributes changingRevision or checkModified

[Carlton Brown <cb...@gmail.com>]

I have observed that TTL rules are not applied when a URL resolver uses 
the changingPattern or checkmodified attribute.

For example, a definition like:
<url name="thirdparty" changingPattern=".*SNAPSHOT" 
latest="latest-revision" checkmodified="true">

does not respect the TTL, but if you remove changingPattern and 
checkmodified, then it complies with the TTL.

I believe it is preferable that the TTL should be effective even if 
these properties are specified on the resolver.   If my cache is fully 
populated, then an infinite TTL should permit me to work comletely offline.

Does anyone agree/disagree that a JIRA should be opened for this?

Thanks,
Carlton