The install task is for copying entire modules into a repository. You typically don't do surgery on the artifacts, filtering by type or classifier, at this point. Once it's in your repository, you use the retrieve task to pull specific artifacts from dependencies.
Perhaps you can explain your use case a little more, and demonstrate what you hope to accomplish with the install task. --Kirby Sent from my mobile device On Jan 28, 2014, at 1:30 PM, Andy Redhead <a...@far2gone.com> wrote: > Hi, > Thanks for your reply and if I was using a dependency then I think this would > be sufficient. > > What I really need is the equivalent for the install task. > > Cheers, Andy > > On 28 Jan 2014 14:44, David Weintraub <qazw...@gmail.com> wrote: >> >> There are a couple of things you need: >> >> * You need to add the following line to the top of your ivy.xml file: >> >> <ivy-module version="1.0" xmlns:maven="http://maven.apache.org";> >> >> Note the "xmlns" declaration. It doesn't matter where it points to (I like >> using the URL of the project), you just need to declare the namespace. >> >> * Now, you can use that Maven classifier in your dependency declaration: >> >> <dependency org="net.sf.json-lib" >> name="json-lib" >> rev="2.4" >> conf="compile->default"> >> <artifact name="json-lib" >> type="jar" >> ext="jar" >> maven:classifier="jdk15"/> >> </dependency> >> >> >> -- >> David Weintraub >> qazw...@gmail.com >> >> ================================================ >> Sure, call me crazy. They called Eddie Antar crazy too, but >> look at these low, low prices on all of these famous name brand appliances. >> >> >> On Jan 28, 2014, at 8:40 AM, a...@far2gone.com wrote: >> >>> Hi, >>> >>> I've been having a go at using the Ivy Install ant task to create a local >>> repository based on libraries downloaded from maven central. >>> >>> Having gone along with the tutorial, all seemed to be working :) >>> >>> Until... >>> >>> One of the dependencies in my project is json-lib. >>> >>> It seems that the json-lib project uses a maven classifier to discriminate >>> between jars suitable for different versions of the jvm. >>> >>> If I were just declaring a dependency I think I could do this: >>> >>> <dependency> >>> <groupId>net.sf.json-lib</groupId> >>> <artifactId>json-lib</artifactId> >>> <version>2.4</version> >>> <classifier>jdk15</classifier> >>> </dependency> >>> >>> However, I'm using install tasks that look like: >>> >>> <ivy:install organisation="log4j" module="log4j" revision="1.2.17" >>> from="chain" >>> to="fs1" transitive="true" overwrite="true"/> >>> >>> How should I declare the "classifier" on an "install" task? >>> >>> Thanks, Andy >>
