axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] Commented: (AXIS2-4571) Axis2 JARS not in sync between standard and backup(?) repos
Date Tue, 08 Dec 2009 09:50:18 GMT


Glen Mazza commented on AXIS2-4571:

Thanks very much Brian for clarifying things.

I was not able to duplicate this problem at all on my Linux machine--everything is running
fine--it was only on Windows at work where I was having this difficulty.  I don't know what
the situation there was, but as long as the repo1 and repo2 machine is the same (and my Linux
box is confirming that) this issue can be closed.

It would be nice if the Maven team could get rid of the (and
other) aliases--just keep the main one listed in the Super POM.  For newbies like me it causes
a lot of confusion as people think the repos are different and then end up explicitly listing
both and/or checking the artifacts between the two, etc.  Of course, removing that alias would
break a lot of POM's, but it should be a simple matter to fix (or alias in their own hosts
file on their end), and, long term, it would be less confusing for everyone.


> Axis2 JARS not in sync between standard and backup(?)
> -----------------------------------------------------------------------------------------------------------------------
>                 Key: AXIS2-4571
>                 URL:
>             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 (
and  (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
(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 repo.
> Also, when I run the "mvn clean install" command on my POM file at [2] with and without
the explicit "" 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
are exactly the same as; 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]
> [2] (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.

View raw message