Quoting Gilles Scokart <[EMAIL PROTECTED]>:
-----Original Message-----
From: Richard Suematsu [mailto:[EMAIL PROTECTED]
Sent: mardi 30 octobre 2007 4:13
To: [email protected]
Subject: A little more info
First, should the jar be in there? Is this just a mistake, or is it
intentional? I seem to remember the JAI project having native code and
therefore must be installed, but I might be mixing that up with Java 3d.
If the dependency is optional, why does my build break if it can't find
the jar?
You are right. But I'm not sure Ivy could do something else.
I don't have a working ivy installation at hand, so I can't try it
now. But I thought if a dependency is explicitly declared 'optional'
in pom.xml, the ivy.xml generated would keep it in a separate conf?
At any rate, we usually deal with this kind of situation by taking
that generated ivy.xml, modifying it with finer conf definitions, and
putting it in an internal repo so it overrides the original pom.xml.
For instance, the latest log4j 1.2.15 release added bunch of
dependencies like jmx and jms, which aren't necessary if you never
intend to manage logging in a jmx console, or to send logging to a
message queue. So we have a modified ivy.xml that puts these
dependencies into separate confs which don't get activated with the
default dependency mappings.
HTH.
--
Jing Xue
