Deploying to travis results in error in opening zip file

using java and maven

Once deploying in travis resulting in corrupt jars, for example by using maven 2.2.1 (which does not following 301 redirects; if you look at the .pom or jar that are downloaded into your local repository, you will see the 301 HTML that was delivered from the server), these jars seems to be cached by travis. They can be removed in the travis local .m2 directory, but when fixing the problem and deploying anew, the cached corrupt jars will be "downloaded" into the local .m2 and results in the same error. Waiting a day or so, this cache seems to be updated so that the travis errors "error in opening zip file" disappear at least.