Hi there fnord,
I'm going to guess that you are collapsing your classpath via a copy
operation, and you're ending up with some of the jars being source and some of
them being runtimes, is that right? Further, I'm going to assume you got your
jars from maven, perhaps via the ivy:install task? Is that right?
If so, then what is happening is:
- The jars from maven have many configurations, one of which is source, and
includes the source jar.
- The default configuration mapping is *->*
- Therefore, by default ivy includes all artifacts.
So, if you add something like:
<configurations defaultconfmapping="default->default">
<conf name="default" />
</configurations>
Then you should be good.
(change the conf name as per your requirements)
Cheers
-Ben
--
Benjamin Damm
Silver Spring Networks
650-298-4200 x201
On Tuesday 31 March 2009 14:06:16 fnord wrote:
> My ivy.xml (with a few dependencies removed for brevity) looks like this:
>
> <ivy-module version="2.0">
> <info organisation="espn" module="espn_itk_core"/>
> <configurations>
> <conf name="runtime" description="" />
> </configurations>
> <dependencies>
> <dependency org="commons-beanutils" name="commons-beanutils"
> rev="1.7.0"/>
> <dependency org="commons-digester" name="commons-digester"
> rev="1.6"/>
> <dependency org="commons-collections" name="commons-collections"
> rev="3.2"/>
> <dependency org="commons-logging" name="commons-logging"
> rev="1.1"/> </dependencies>
> </ivy-module>
>
> I'm getting runtime jars for everything but commons-digester, which is
> giving me a source jar.
>
> Am I missing something?
>
>
> thanks,
> fnord
