ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <gscok...@gmail.com>
Subject RE: IDEA project setup, or "Is there a standard way to deal with source and library artifacts?"
Date Wed, 21 Feb 2007 09:26:46 GMT
I did that by adding the src and the javadoc artefacts into the list of
artefacts in the ivy.xml, and I put some dedicated values in the type
attribute ('src' and 'javadoc') in order to be able to retrieve them
separately (for example, when I setup a path, I don't need them).

Hope it help,

Gilles

> -----Original Message-----
> From: Davide Baroncelli [mailto:baroncelli@yahoo.com]
> Sent: mercredi 21 février 2007 10:14
> To: ivy-user@incubator.apache.org
> Subject: IDEA project setup, or "Is there a standard way to deal with
> source and library artifacts?"
> 
> Hello,
> as part of our build process (which is "ivy-ized" in that every subproject
> declares its dependencies and its publications through ivy) we would like
> to provide some sort of standard way of not only retrieving the
> dependencies when building, but some sort of support for retrieving not
> only the binary dependencies but also their source and javadoc packages. I
> wondered what is the best way to deal with this in ivy: it seems there is
> no explicit way to declare source and javadoc artifacts, is it there?
> 
> Thanks,
> Davide Baroncelli.



Mime
View raw message