POM in mirror is bad but central is good?

[Mike Perham <Mi...@webifysolutions.com>]

central:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/comm
ons-logging-1.0.4.pom
mirror:
http://python.planetmirror.com/pub/maven2/commons-logging/commons-loggin
g/1.0.4/commons-logging-1.0.4.pom

The POM for commons-logging 1.0.4 is good in repo1 but invalid in the
mirror (looks like it is the M1 version).  The good version has a
filestamp in November but the bad version has a filestamp from
yesterday.  How can a mirror version change without the central version
changing?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: POM in mirror is bad but central is good?

[Emmanuel Venisse <em...@venisse.net>]

we had a problem yesterday on central repository, so some poms was invalid and mirror have 
replicated them. I think they'll be fixed in the next synchronisation with central repository.

Emmanuel

Mike Perham a écrit :
> central:
> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/comm
> ons-logging-1.0.4.pom
> mirror:
> http://python.planetmirror.com/pub/maven2/commons-logging/commons-loggin
> g/1.0.4/commons-logging-1.0.4.pom
> 
> The POM for commons-logging 1.0.4 is good in repo1 but invalid in the
> mirror (looks like it is the M1 version).  The good version has a
> filestamp in November but the bad version has a filestamp from
> yesterday.  How can a mirror version change without the central version
> changing?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org