Seems like it must be a caching issue. Or in some bizzarro universe, maven central is serving up a corrupted zip