The fact that it is not a direct dependency does not really matter in this particular case. You have a bad jar in your (transitive) deps, like it or not.
I would simply add a dependency on a newer version of this jar in your own project eg [3.8]. I would also encourage the "xom" people to produce a new version that depends on a build of icu4j that is not broken. And then encourage the "jaxen" people to upgrade to that xom version. Wayne On Mon, Oct 6, 2008 at 1:42 AM, qrtt1 <[EMAIL PROTECTED]> wrote: > > Hi Wayne, > > Thanks for your suggestion. > > but it's not a direct dependency. > > jaxen use xom and xom use icu4j. > > Maybe just ignore the warnings and errors. > > > Wayne Fay wrote: >> >> As I suspected, there are several newer versions (3.4.4, 3.6.1, 3.8): >> http://repo1.maven.org/maven2/com/ibm/icu/icu4j/ >> >> Try the latest v3.8 instead. >> >> Wayne >> >> On Sun, Oct 5, 2008 at 11:44 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: >>> It appears this class/jar is the source of your problems. Perhaps IBM >>> has a newer version of icu4j? >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/Problem-when-mvn-site%3Asite-%60Generating-%22Dependencies%22-report%27-tp19831145p19834001.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
