You most probably need to set your resolvers to be Maven compatible
(in your settings file) e.g.,

        <property name="ivy.shared.m2.ivy.pattern"
                
value="[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]"
                override="false"/>

        <property name="ivy.shared.m2.artifact.pattern"
                
value="[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]"
                override="false"/>

                <url name="java.net" m2compatible="true">
                        <ivy 
pattern="http://download.java.net/maven/2/${ivy.shared.m2.ivy.pattern}"/>
                        <artifact 
pattern="http://download.java.net/maven/2/${ivy.shared.m2.artifact.pattern}"/>
                </url>

http://ant.apache.org/ivy/history/latest-milestone/resolver/url.html

There is a complete settings file here

http://codegeo.org/repos/codegeo/build/trunk/ivysettings.xml

Cheers,
Geoff





On Fri, Sep 23, 2011 at 2:08 AM, teknokrat <igor.apte...@nomura.com> wrote:
> We store a number of supplementary artifacts with out main one in our
> maven repo. For the life of me I cannot get Ivy to ever resolve them.
> I use the following in my Ivy file:
>
> <dependency name="module" rev="latest.integration">
>  <artifact name="module" conf="config" type="config" ext="jar"
> e:classifier="config"/>
>  <artifact name="module"/>
> </dependency>
>
> config is a configuration defined in the configurations section.
> I expect this to download module.jar and module-config.jar, but
> only new versions of module.jar are ever downloaded.
> Even though module-config.jar has changed as well.
>
> What is the correct way to do this?
>
> Thanks
>
>

Reply via email to