ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <>
Subject Re: Exclude Clarifications
Date Fri, 11 Jan 2008 09:25:50 GMT
When you are facing some bad metadata, I fear that you have no choice than
fixing them.

You can either setup your own repository in which you put the correct ivy
file (or pom file).

If you don't want this, you can use transitive=false, or you have to list
the dependencies you want to include.

There is currently no pattern matching that can be used to to filter the
transitive dependencies.


2008/1/10, lukasbradley <>:
> I would like to exclude all dependencies that are not the concrete
> dependency
> itself.
> For example, Hibernate 3.2.5 has *tons* of dependencies that I do not need
> to include.  Great examples are the inclusion of both Proxool and C3P0
> database pooling jars.  I don't want those around.
> I have tried the following, without success.  I'm attempting to exclude
> everything that isn't from the "org.hibernate" organization.
>         <dependency org="org.hibernate" name="hibernate" rev="">
>             <exclude org="(?!org.hibernate)" matcher="regexp"></exclude>
>         </dependency>
> To summarize, I want ONLY the Hibernate 3.2.5 jar to be added as a
> dependency, and nothing more.
> Am I on the right track, or is there an easier way to do this?
> Lukas
> --
> View this message in context:
> Sent from the ivy-user mailing list archive at

Gilles Scokart

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message