Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of richard.mauri@sap.com
 designates 155.56.66.99 as permitted sender)
From: "Mauri, Richard" <richard.mauri@sap.com>
To: Maven Users List <users@maven.apache.org>
Subject: Re: maven won't resolve from central log4j:log4j:1.2.8 through
 1.2.15
Thread-Topic: maven won't resolve from central log4j:log4j:1.2.8 through
 1.2.15
Thread-Index: 
 AQHPOkSj6FlH9DZ8P0mUCy5j0TRdE5rZ3NUAgABJWgCAAG4OAP//sjUAgACCs4CAAAH5gIADBEiA
Date: Wed, 12 Mar 2014 21:36:25 +0000
Message-ID: <CF462106.121C%richard.mauri@sap.com>
References: <CF3F698F.FEB%richard.mauri@sap.com>
 <CALy+7UkrjBKRZYhYtHQEjePF_k9gQk_1OiQ73Fp1Z_mRTGm3EQ@mail.gmail.com>
 <CAKDUN1vZq3etVMPG_D5n90w6a43Ksc0GC3pOfP8zedqj6Tm5XQ@mail.gmail.com>
 <CALy+7UmP+e5r9P9_CwzNLXLtr0Uz9HYE=eJ7G7n7yN4yDPx3yw@mail.gmail.com>
 <CF4329DB.10B4%richard.mauri@sap.com>
 <CAPCUOdFYPyGaGbH94jZBcL+6y1wOg3VGevONWJr9oSg8Obh7_A@mail.gmail.com>
 <CAKDUN1t_8SZT6RgZrBQb_h7LoQQ=DKsu0suyy5oaroV-orPqOA@mail.gmail.com>
In-Reply-To: 
 <CAKDUN1t_8SZT6RgZrBQb_h7LoQQ=DKsu0suyy5oaroV-orPqOA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.9.131030
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <330915EEF23C6D4DBB1A73A887F9A8C3@exchange.sap.corp>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi, any word on how to fix the maven central repo so we can proceed with
resolving (mvn dependency:tee) log4j:log4j:[1.2.8] ?

It=B9s curious why we can request with soft version 1.2.8 but not absolute
[1.2.8]

What has to happen to fix the maven central repos?

On 3/10/14, 9:32 AM, "Anders Hammar" <anders@hammar.net> wrote:

>Yes, something seems wrong with the metadata file. It should list all
>versions.
>
>/Anders (mobile)
>Den 10 mar 2014 17:25 skrev "Adrien Rivard" <adrien.rivard@gmail.com>:
>
>> Does'nt seem to work for me either when hitting maven central directly.
>> Works ok when using my usual MRM.
>>
>> If I'm not wrong
>> http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml
>>should
>> return all versions while it returns only 2 .
>>
>>
>>
>>
>> On Mon, Mar 10, 2014 at 4:37 PM, Mauri, Richard <richard.mauri@sap.com
>> >wrote:
>>
>> > I am still having trouble.
>> > It certainly should be easy to reproducee no?
>> > It is a trivial settings.xml and pom.xml and mvn dependency:tree goal
>> >
>> > Thanks for helping, but please keep at it :-)
>> >
>> > On 3/10/14, 6:15 AM, "Wayne Fay" <waynefay@gmail.com> wrote:
>> >
>> > >>> Where did this repo.maven.apache.org url come from?
>> > >>
>> > >> Wayne, it's a correct URL for the central repository. It's the one
>>we
>> > >> define in the super-POM since Maven 3.0.something.
>> > >
>> > >Doh, well ignore that then. I should have done 30 seconds of
>>searching
>> > >before sending that one. :)
>> > >
>> > >But just FYI, when I myself tried accessing that URL last night, I
>>had
>> > >problems in my browser. First it was HTTPS problems as the URL did
>>not
>> > >match the server name being reported (I have the HTTPS Everywhere
>> > >plugin turned on). I clicked "ignore" and went to the site and got
>> > >HTTP 404 errors at /log4j/log4j/maven-metadata.xml so I moved up to
>> > >/log4j/log4j and had the same errors. I did not grab the error but it
>> > >was something related to Varnish cache - when I cause a 404 now, the
>> > >error appears different.
>> > >
>> > >So at the very least, the mirror I was on (fastly.net) was having
>> > >issues - and potentially this was mirrored to others, possibly
>> > >explaining the troubles (??). I had no such trouble hitting the old
>> > >standby of repo1.maven.org and resolving the files etc. These errors
>> > >made me question the URL entirely.
>> > >
>> > >I hit it again just now and dns sends me to fastly.net again but this
>> > >time the files are there.
>> > >
>> > >So, I would ask Richard to try again and see if things work better
>> > >today, or if he is having the same troubles.
>> > >
>> > >Wayne
>> > >
>> > >---------------------------------------------------------------------
>> > >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
>> >
>> >
>>
>>
>> --
>> Adrien Rivard
>>


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