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? Otherw
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
On Mon, Jun 14, 2010 at 5:58 PM, Zac Thompson wrote:
> Is there a place to report issues with the contents of maven centr
http://jira.codehaus.org/browse/MEV
/Anders
On Mon, Jun 14, 2010 at 23:58, Zac Thompson wrote:
> Is there a place to report issues with the contents of maven central?
> Or does it need to be reported to each project's maintainers?
>
>
> https://repository.sonatype.org/content/repositories/centr
Is there a place to report issues with the contents of maven central?
Or does it need to be reported to each project's maintainers?
https://repository.sonatype.org/content/repositories/central/org/codehaus/woodstox/stax2-api/3.0.1/
the jar.sha1 file reads
88985bfab2394cf8e56fcbd97cd44f7cac7bf8ca
