axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4571) Axis2 JARS not in sync between standard http://repo1.maven.org/maven2 and backup(?) http://repo2.maven.org/maven2 repos
Date Tue, 08 Dec 2009 04:22:18 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787298#action_12787298
] 

Brian Fox commented on AXIS2-4571:
----------------------------------

I can confirm without question that repo1 and repo2 are the same machine since I've been maintaining
it.

Dns lookup confirms this:
Pinging repo1.maven.org [38.97.124.18] with 32 bytes of data:
Reply from 38.97.124.18: bytes=32 time=52ms TTL=48
Reply from 38.97.124.18: bytes=32 time=51ms TTL=48

Pinging repo2.maven.org [38.97.124.18] with 32 bytes of data:
Reply from 38.97.124.18: bytes=32 time=51ms TTL=48
Reply from 38.97.124.18: bytes=32 time=53ms TTL=48

Also the nginx conf:
  server {
    server_name  repo2.maven.org test.repo2.maven.org test.repo1.maven.org repo1.maven.org
repo4.maven.org;


Unfortunately the circumstantial evidence listed above isn't enough for me to say what is
actually happening in your config, but it is certainly not because of a difference between
the urls.

> Axis2 JARS not in sync between standard http://repo1.maven.org/maven2 and backup(?) http://repo2.maven.org/maven2
repos
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4571
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4571
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Glen Mazza
>
> The Axis2 1.5.1 JARs appear to be out of sync between the two main Maven repos (http://repo1.maven.org/maven2
and http://repo2.maven.org/maven2).  (When one views these directories from a web browser,
the former redirects to the latter giving the false impression that they have the same files.)
 
> In particular, not all of the Axis2 1.5.1 jars are in the main http://repo1.maven.org/maven2
(the one pointed to by the Super POM[1]), requiring users to have to explicitly declare the
other repository in their POM file[2] in order to get the needed JARs downloaded for their
clients to work.  If they don't make this declaration, Maven complains about many missing
files/data corruption errors from the main Super POM http://repo1.maven.org/maven2 repo.
> Also, when I run the "mvn clean install" command on my POM file at [2] with and without
the explicit "http://repo2.maven.org/maven2" repo declaration, I can see by viewing my local
repository that the Axis2 JARs downloaded from the two repos are out of sync:  axis2-adb-codegen,
axis2-codegen, axis2-java2wsdl, axis2-jaxbri, axis2-xmlbeans, for example, are different between
the two repos.  (Size and timestamp and frequently even existence of file.)
> The task here is to make sure that the Axis2 1.5.1 jars in http://repo1.maven.org/maven2
are exactly the same as http://repo2.maven.org/maven2; also, to check that the POM file in
[2] below can run ("mvn clean install") *without* needing to explicitly declare the latter
repo.  (By default, Axis2 shouldn't need external repo declarations in order to be used, correct?)
> [1] http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom.html#pom-relationships-sect-super-pom
> [2] http://www.jroller.com/gmazza/entry/soap_client_with_axis2 (the pom under Step #4).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message