Good day,
I have a question w.r.t exclusions in the dependency tag of the ivy.xml:
Question 1
With below exclusion I would have thought that all the dependencies of
commons-configuration would be excluded except for commons-configuration. But
everything, including commons-configuration are excluded.
<dependency org="commons-configuration" name="commons-configuration"
rev="1.9">
<exclude org="*" name="*"/>
</dependency>
Question 2
Making the POM file of the below ivy.xml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd";>
<info organisation="za.co.absa" module="ESF" revision="2.5"/>
<publications>
<artifact type="pom" ext="pom"/>
<artifact type="jar" ext="jar"/>
</publications>
<dependencies>
<dependency org="org.apache.commons" name="commons-email" rev="1.3.1"
transitive="false"/>
<dependency org="com.fasterxml.jackson.core" name="jackson-annotations"
rev="2.6.3" transitive="false"/>
<dependency org="com.fasterxml.jackson.core" name="jackson-core"
rev="2.6.3" transitive="false"/>
<dependency org="com.fasterxml.jackson.core" name="jackson-databind"
rev="2.6.3" transitive="false"/>
<dependency org="log4j" name="log4j" rev="1.2.4" transitive="false"/>
</dependencies>
</ivy-module>
Results in:
<modelVersion>4.0.0</modelVersion>
<groupId>za.co.absa</groupId>
<artifactId>ESF</artifactId>
<packaging>pom</packaging>
<version>2.5</version>
<dependencies>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-email</artifactId>
<version>1.3.1</version>
<optional>false</optional>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.6.3</version>
<optional>false</optional>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.6.3</version>
<optional>false</optional>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.4</version>
<optional>false</optional>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
When you do a retrieve in IVYDE, then of the above, then nothing gets retrieved
except for ESF 2.5. Surely the other dependencies should have been retrieved,
except for their transitive dependencies?
[cid:[email protected]]
<?xml version="1.0" encoding="ISO-8859-1"?>
<ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd";>
<info organisation="za.co.absa" module="ZZZZ_EAR"/>
<dependencies>
<dependency org="za.co.absa" name="ESF" rev="2.5"/>
<exclude org="*" ext="*" type="source"/>
<exclude org="*" ext="*" type="javadoc"/>
</dependencies>
</ivy-module>
Kind Regards
Linda van Rensburg
Developer ABSA Bank, South Africa
[email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>
Important Notice:
Absa is an Authorised Financial Services Provider and Registered Credit
Provider,
registration number: NCRCP7. This e-mail and any files transmitted with it may
contain information that is confidential, privileged or otherwise protected
from
disclosure. If you are not an intended recipient of this e-mail, do not
duplicate
or redistribute it by any means. Please delete it and any attachments and
notify
the sender that you have received it in error. Unless specifically indicated,
this
e-mail is not an offer to buy or sell or a solicitation to buy or sell any
securities,
investment products or other financial product or service, an official
confirmation of
any transaction, or an official statement of Absa. Any views or opinions
presented
are solely those of the author and do not necessarily represent those of Absa.
This e-mail is subject to terms available at the following link:
http://www.absa.co.za/disclaimer.
The Disclaimer forms part of the content of this email. If you are unable to
access
the Disclaimer, send a blank e-mail to [email protected] and we will send
you a
copy of the Disclaimer. By messaging with Absa you consent to the foregoing.
By emailing Absa you consent to the terms herein. This email may relate to or
be sent
from other members of the Absa Group.
