hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Hbase/IvyPrimer" by KayKay
Date Sun, 10 Jan 2010 03:27:04 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "Hbase/IvyPrimer" page has been changed by KayKay.
http://wiki.apache.org/hadoop/Hbase/IvyPrimer?action=diff&rev1=2&rev2=3

--------------------------------------------------

  
  This would clear the ivy cache and start all over again. This is needed only in the worst
case and not for every build. 
  
- Usually this happens when the publisher republishes the binary in the repository making
the client cache out of sync, with the server.  This does not happen. 
+ Usually this happens when the publisher republishes the binary in the repository (for the
same version, after a release) making the client cache out of sync, with the server.  For
most of the open source projects will well-defined release process, this does not happen.

  
    * I do not need to connect to the internet from the build server. What are the options
now. 
  
- * Set up a directory structure to a repository listed ( Say , http://repo2.maven.org/maven2/
).  
+    * Set up a directory structure similar to a repository listed ( Say , http://repo2.maven.org/maven2/
).  
- * For all the projects (And the versions) that you need , create the directory structure
exactly the same as those in the repository. 
+    * For all the projects (And the versions) that you need , create the directory structure
exactly the same as those in the repository. 
- * Modify ivy/ivysettings.xml to add a file/directory based resolver at the beginning. 
+    * Modify ivy/ivysettings.xml to add a file/directory based resolver at the beginning.

- * In the chain of resolvers, add the new resolver right on top before everything else (
as the order matters). 
+    * In the chain of resolvers, add the new resolver right on top before everything else
( as the order matters). 
  
  So - now we are good with the build able to complete from our internally controlled repository
as opposed to being exposed to the outside world. 
  

Mime
View raw message