ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kay Kay <>
Subject Issue with maven snapshot pull strategy
Date Fri, 15 Jan 2010 20:12:16 GMT
We are trying to build our project based on ivy , that has dependencies 
on some mvn snapshots present in the apache snapshot repository.

I have added the details to the same at - .

Our ivy settings file looks something like as follows. (Sample module- 
org.apache.hadoop / hadoop-core ).

    <property name=""  value=""  override="false"/>
   <property name=""  value=""
   <property name="maven2.pattern"  value="[organisation]/[module]/[revision]/[module]-[revision]"/>
   <property name="maven2.pattern.ext"  value="${maven2.pattern}.[ext]"/>

   <settings defaultResolver="default"/>
     <!--ibiblio resolvers-->
     <ibiblio name="maven2"  root="${}"  m2compatible="true"/>
     <ibiblio name="apache-snapshot"  root="${}"  m2compatible="true"
         checkmodified="true"  changingPattern=".*SNAPSHOT"/>

     <chain name="default"  dual="true">
       <resolver ref="maven2"/>
       <resolver ref="apache-snapshot"  />


When a new release is made and symlinked to 0.21.0-SNAPSHOT, and when we 
do ivy-retrieve - what we want is to get the new jars down to 
~/.ivy2/cache and used by the build process. But that does not seem to 
be happening.  Any workaround for the same that exists ?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message