(Full disclosure: I'm new to Ivy as well, so maybe one of the gurus can chime in and verify this)
You have both "type" and "classifier" attributes at your disposal. In your ivy file you can say that you only want type "jar" or type "src", whatever. You can also specify type in your resolve Ant task. If you have a single build that produces two artifacts of type "jar" then you would use the classifier to distinguish between them so that you don't end up with a name collision. For example, if you have a build that produces a client API and implmentation, your publish section of your ivy file would need to list one of them with a classifier. With a classifier you could have both myjar-1.0.jar and myjar-1.0-client.jar. Josh On Mon, May 11, 2009 at 11:09 AM, imihov <[email protected]> wrote: > > Unfortunately, I cannot find anything in the Ivy documentation on usage of > the 'classifier' pattern/attribute. I see in the code that it is used in > the > POM parser/reader, but nothing outside of that. > > Let's say that I had the above pattern in my settings file. How would I > tell > Ivy to retrieve the 'src' artifact? How would I map the configuration to > it? > > Thanks, > --ivo > -- > View this message in context: > http://www.nabble.com/Settings---configuration-for-retrieving-artifacts-with-classifier-%28javadoc%2C-src%2C-etc.%29-tp23487693p23488546.html > Sent from the ivy-user mailing list archive at Nabble.com. > >
