Yes, these are all related; we've also received a number of new reports
over the last few hours.
The CDN provider is asking for traceroute information from affected
users:
$ traceroute -n repo1.maven.org
Regards,
Jason
On Mon, Nov 05, 2012 at 04:15:25PM +0100, Martin Hoeller wrote:
> Hi!
>
> Could it be MVNCENTRAL-252?
> See also this thread some weeks ago:
> http://maven.40175.n5.nabble.com/Broken-link-for-avalon-td5726894.html
>
> - martin
>
>
> On 05 Nov 2012, Brian Fox wrote:
>
> > N oone has been blacklisted in a while. Can you give us the headers like
> > shown here:
> >
> >
> > $ curl -I
> > http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-api/4.3.1/avalon-framework-api-4.3.1.jar
> > HTTP/1.1<http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-api/4.3.1/avalon-framework-api-4.3.1.jarHTTP/1.1>
> > 200 OK
> > Accept-Ranges: bytes
> > Content-Type: application/java-archive
> > Date: Thu, 25 Oct 2012 10:07:48 GMT
> > Last-Modified: Thu, 15 Feb 2007 20:44:01 GMT
> > Server: ECAcc (dfw/F489)
> > X-Cache: HIT
> > Content-Length: 33218
> >
> >
> >
> > Then we can go to the CDN and see what's up.
> >
> >
> > On Mon, Nov 5, 2012 at 9:05 AM, eugene <[email protected]> wrote:
> >
> > > Hello Ron,
> > >
> > > As a matter of fact we do have our own repo, nexus based.
> > >
> > > We have A LOT of projects that we have to "mavenize", thus, yes I think
> > > that
> > > maven thinks we are doing something wrong. But then again, all that we do
> > > is
> > > get some jars from it, nothing else, nothing more, isn't maven suppose to
> > > do
> > > that in the first place? I'm confused.
> > >
> > > Ok, so how do we get out of the blacklist? Whom do we contact, etc?
> > >
> > > Thank You,
> > > Eugene.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
