cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Shepherd <darren.s.sheph...@gmail.com>
Subject Re: 4.2.1 package issues
Date Thu, 17 Oct 2013 18:15:55 GMT
On 10/17/2013 11:06 AM, Bjoern Teipel wrote:
> Compilation failure:
> [ERROR] error: error reading
> /home/bteipel/.m2/repository/org/apache/axis2/mex/1.5.4/mex-1.5.4-impl.jar;
> error in opening zip file
> [ERROR] error: error reading
> /home/bteipel/.m2/repository/org/apache/axis2/axis2-mtompolicy/1.5.4/axis2-mtompolicy-1.5.4.jar;
> error in opening zip file
> [ERROR] error: error reading
> /home/bteipel/.m2/repository/org/apache/ws/commons/axiom/axiom-dom/1.2.10/axiom-dom-1.2.10.jar;
> error in opening zip file
> [ERROR] error: error reading
> /home/bteipel/.m2/repository/org/opensaml/opensaml1/1.1/opensaml1-1.1.jar;
> error in opening zip file
> [ERROR] error: error reading
> /home/bteipel/.m2/repository/commons-lang/commons-lang/2.3/commons-lang-2.3.jar;
> error in opening zip file

Typically this happens when a maven mirror doesn't exist any more, 
moved, is having issues, etc.  Actually open up one of those bad jars in 
a text editor and good chance there is some HTML error document in there.

You can try just deleteing the folders that contain the bad jars and 
hopefully it will download them from a good location.  In general its a 
swell idea to use a maven proxy, Nexus or Artifactory, they usually do a 
better job of avoiding these errors.

Darren


Mime
View raw message