Yeah, that's what I was afraid of. I've tried the no-cache approach, and if it worked, it would be perfect since very few of my programs take any time to load at all- actually, I tried that with a problem with HTML in Swing components not rendering properly in cached versions (remember?
), but I had problems with clients simply ignoring that.
Anyway, it's a problem I've been looking for a solution to for quite some time. I'd like to find a way that didn't involve changing the Jar name, half for my own sanity and half to not break links I post to it on forums, etc. But it's not the end of the world either way, I suppose. Thanks again for the input though, I know next to nothing about deployment and web stuff.