Agreed ... I'm sure they tried to re-release. So I'm using dependencyManagement to force 3.0.2 :)
But if you don't allow it, why is central's .sha1 wrong for the corresponding jar file in this case? Alternatively, would you consider allowing re-release for jars/checksums that don't match? Otherwise it seems there is no simple way to correct them once broken. I will follow up with the woodstox folks and point them towards the MEV link. Zac On Tue, Jun 15, 2010 at 8:52 AM, Brian Fox <[email protected]> wrote: > This implies to me that they attempted to re-release the same jar > after it was synced to central. We don't allow that, hence the > difference between the source repo and central > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
