You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Mauri, Richard" <ri...@sap.com> on 2014/03/07 21:34:28 UTC
maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Using mvm 3.1.1 with a pom.xml with a dependency on log4j version [1.2.8]
- it will not resolve
Similar for required versions up to and including [1.2.15]
It¹s not an option for us to just go to the later log4j like [1.2.17]
What¹s going on here?
If we request an open ended 1.2.8 then it resolves ok !
Here¹s an example session
i836228@SJCM00561975A> mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building testlog4j 1.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
Downloading:
http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml
Downloading: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
Downloaded: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
(352 B at 0.7 KB/sec)
Downloaded:
http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml (352 B
at 0.6 KB/sec)
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.025s
[INFO] Finished at: Fri Mar 07 12:31:54 PST 2014
[INFO] Final Memory: 6M/81M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project testlog4j: Could not resolve
dependencies for project ariba.testlog4j:testlog4j:jar:1.0-SNAPSHOT:
Failed to collect dependencies at log4j:log4j:jar:[1.2.8,1.2.8]: No
versions available for log4j:log4j:jar:[1.2.8,1.2.8] within specified
range -> [Help 1]
Here is a pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>ariba.testlog4j</groupId>
<artifactId>testlog4j</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>jar</packaging>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>[1.2.8]</version>
</dependency>
</dependencies>
</project>
Here is a .m2/settings.xml
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<proxies>
<proxy>
<id>sap</id>
<active>true</active>
<protocol>http</protocol>
<host>proxy.ariba.com</host>
<port>8080</port>
</proxy>
</proxies>
<profiles>
<profile>
<id>alwaysActiveProfile</id>
<repositories>
<repository>
<id>MavenCentralRepo1</id>
<name>maven Central Repo1</name>
<url>http://repo1.maven.org/maven2</url>
<layout>default</layout>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
</activeProfiles>
</settings>
On 3/6/14, 9:16 AM, "Venkata Suresh Kumar Pamidipati"
<su...@oracle.com> wrote:
>Hi mgainty,
>
>Thanks for the response and information. I will contact the number given
>below.
>
>Thanks & Regards,
>Suresh
>
>
>----- Original Message -----
>From: mgainty@hotmail.com
>To: users@maven.apache.org, suresh.pamidipati@oracle.com
>Sent: Thursday, March 6, 2014 6:39:54 PM GMT +05:30 Chennai, Kolkata,
>Mumbai, New Delhi
>Subject: RE: Invalid signature file digest for Manifest main attributes
>
>Hi Suresh
>
>
>
>Your best solution will come from Oracle Support India
>They are supposed to know this information and will be able to assist you
>with your problem
>Oracle India Support Line number is +91.22.66796200
>If Oracle India is unable to assist you ..we can find a resource on this
>side of the planet to help you
>
>
>Warm Regards
>
>
>
>
>
>> Date: Wed, 5 Mar 2014 19:19:44 -0800
>> From: suresh.pamidipati@oracle.com
>> To: users@maven.apache.org
>> Subject: Invalid signature file digest for Manifest main attributes
>>
>> Hi,
>>
>> I am trying to build our project using maven. I have included multiple
>>dependency jars in pom.xml and I am trying to build distribution jar
>>using assembly:assembly goal. The command "mvn assembly:assembly"
>>resulted in the below error.
>>
>> [ERROR] Failed to execute goal
>>org.apache.maven.plugins:maven-assembly-plugin:2.4:assembly
>>(default-cli) on project my-plugin: Execution default-cli of goal
>>org.apache.maven.plugins:maven-assembly-plugin:2.4:assembly failed:
>>Invalid signature file digest for Manifest main attributes -> [Help 1]
>>
>> Two of the dependency jars when present together was causing this
>>issue. I tried commenting one of them and mvn assembly:assembly command
>>worked fine. To make it work with both the jars present together, I
>>tried by adding excludes in dependency, assembly and even shade plugin
>>configuration in pom.xml to exclude MANIFEST files of one of those two
>>jars as shown below, but still the same error exists.
>>
>> <configuration>
>> <filters>
>> <filter>
>> <artifact>MyJar1:MyJar1</artifact>
>> <excludes>
>> <exclude>META-INF/*.SF</exclude>
>> <exclude>META-INF/*.DSA</exclude>
>> <exclude>META-INF/*.RSA</exclude>
>> </excludes>
>> </filter>
>> </filters>
>> </configuration>
>>
>> Please let me know how to resolve this error. I am not sure if the
>>exclude statements were being ignored or I am missing some thing here.
>>Any information on this will be really helpful.
>>
>> Thanks & Regards,
>> Suresh
>>
>>
>> ---------------------------------------------------------------------
>> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven won't resolve from central log4j:log4j:1.2.8 through
1.2.15
Posted by "Mauri, Richard" <ri...@sap.com>.
Yes Wayne, I rm -rf ~/.m2/repository
Your questioning implies my test case is not reproducible for you; really
????
On 3/10/14, 9:19 AM, "Wayne Fay" <wa...@gmail.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
>
>Have you used "mvn -U" lately?
>Have you deleted ~/.m2/repository lately? I rarely do this myself, but
>occasionally we hear this solves problems for some users. I might
>suggest a slightly more surgical deletion of ~/.m2/repository/log4j
>rather than the entire repo in this case.
>
>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
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Wayne Fay <wa...@gmail.com>.
> 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
Have you used "mvn -U" lately?
Have you deleted ~/.m2/repository lately? I rarely do this myself, but
occasionally we hear this solves problems for some users. I might
suggest a slightly more surgical deletion of ~/.m2/repository/log4j
rather than the entire repo in this case.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Baptiste Mathus <ml...@batmat.net>.
File an issue there: https://issues.sonatype.org/browse/mvncentral
Cheers
2014-03-12 22:36 GMT+01:00 Mauri, Richard <ri...@sap.com>:
> 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¹s 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" <an...@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" <ad...@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" <wa...@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
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;! <us...@maven.apache.org>
>
Re: maven won't resolve from central log4j:log4j:1.2.8 through
1.2.15
Posted by "Mauri, Richard" <ri...@sap.com>.
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¹s 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" <an...@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" <ad...@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" <wa...@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
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Anders Hammar <an...@hammar.net>.
Yes, something seems wrong with the metadata file. It should list all
versions.
/Anders (mobile)
Den 10 mar 2014 17:25 skrev "Adrien Rivard" <ad...@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" <wa...@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
>
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Adrien Rivard <ad...@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 <ri...@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" <wa...@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
Re: maven won't resolve from central log4j:log4j:1.2.8 through
1.2.15
Posted by "Mauri, Richard" <ri...@sap.com>.
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" <wa...@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
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Wayne Fay <wa...@gmail.com>.
>> 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
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Anders Hammar <an...@hammar.net>.
>
> 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.
/Anders
It is invalid as
> far as I know. I suspect your troubles are related to this. Or
> possibly related to the proxy you have defined.
>
> The correct URL to central is repo1.maven.org:
> http://repo1.maven.org/maven2/log4j/log4j/
>
> which shows these versions under that GA coordinate:
> 1.1.3/ 04-Jan-2007 19:21
> -
> 1.2.11/ 04-Jan-2007 19:21
> -
> 1.2.12/ 04-Jan-2007 19:21
> -
> 1.2.13/ 04-Jan-2007 19:21
> -
> 1.2.14/ 08-Jan-2007 15:56
> -
> 1.2.15/ 30-Aug-2007 17:41
> -
> 1.2.16/ 08-Jan-2011 14:24
> -
> 1.2.17/ 28-May-2012 10:46
> -
> 1.2.4/ 04-Jan-2007 19:21
> -
> 1.2.5/ 04-Jan-2007 19:21
> -
> 1.2.6/ 04-Jan-2007 19:21
> -
> 1.2.7/ 04-Jan-2007 19:21
> -
> 1.2.8/ 04-Jan-2007 19:21
> -
> 1.2.9/ 04-Jan-2007 19:21
> -
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
Posted by Wayne Fay <wa...@gmail.com>.
> Downloading:
> http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml
> Downloading: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
> Downloaded: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml
> (352 B at 0.7 KB/sec)
> Downloaded:
> http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml (352 B
> at 0.6 KB/sec)
Where did this repo.maven.apache.org url come from? It is invalid as
far as I know. I suspect your troubles are related to this. Or
possibly related to the proxy you have defined.
The correct URL to central is repo1.maven.org:
http://repo1.maven.org/maven2/log4j/log4j/
which shows these versions under that GA coordinate:
1.1.3/ 04-Jan-2007 19:21
-
1.2.11/ 04-Jan-2007 19:21
-
1.2.12/ 04-Jan-2007 19:21
-
1.2.13/ 04-Jan-2007 19:21
-
1.2.14/ 08-Jan-2007 15:56
-
1.2.15/ 30-Aug-2007 17:41
-
1.2.16/ 08-Jan-2011 14:24
-
1.2.17/ 28-May-2012 10:46
-
1.2.4/ 04-Jan-2007 19:21
-
1.2.5/ 04-Jan-2007 19:21
-
1.2.6/ 04-Jan-2007 19:21
-
1.2.7/ 04-Jan-2007 19:21
-
1.2.8/ 04-Jan-2007 19:21
-
1.2.9/ 04-Jan-2007 19:21
-
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org