--- Comment #1 from Mark Thomas <> ---
Yes, this is caused by that commit.

The fix looks fairly simple but we are at the limit of what the current
implementation can reasonably do in terms of guaranteeing consistency. Chances
are you are going to end up accessing the resource directly, bypassing the
cache and running the risk of seeing inconsistent results. That said, the
chances of a resource inside a JAR changing should be a lot lower.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to