ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From efe4it <>
Subject Resolving source artefact altered by m:classifier
Date Tue, 22 May 2012 16:09:38 GMT


I recently tried to configure source artifact resolving in IvyDE and 
noticed a side effect of m:classifier attribute of source-typed 

I use Ant-1.8.3, Ivy-2.2.0, IvyDE-2.2.0.beta1-201203282058-RELEASE

My project rely on an "entreprise repository", as suggested in IVY 
tutorial, that I assemble from various public repo.
You may download the example (ivy and settings file included) by running: 
svn co -r 272 --ignore-externals

When ivy:install-ing the module org.apache.ant#ant#1.8.3 (default target 
of buildfile), the module is fetched from "" (see 
attached ant.log file) 

The following files are downloaded: ...

The following files are created in target repository
[ivy:install] 	published ant to
[ivy:install] 	published ant to
[ivy:install] 	published ant to
[ivy:install] 	published ivy to

Noticed all jars have been renamed to "ant.jar" but the ivy file contains
artifacts declaration including "m:classifier"
<artifact name="ant" type="jar" ext="jar" conf="master"/>
<artifact name="ant" type="source" ext="jar" conf="sources"
<artifact name="ant" type="javadoc" ext="jar" conf="javadoc"

I upgraded IvyDE to the last available distibution, but the problem also
occurs when using IVY from ANT.
The artefact definition using m:classifier="sources" make IVY look for the
file named ant-sources.jar while attempting
to resolve source-typed artefact.

I am wondering what I should modify in the installation step to either:
- get rid of m:classifier
- prevent ivy to rename the jars 

What do you think?

View this message in context:
Sent from the ivy-user mailing list archive at

View raw message