kaspersky wrote:
Hi Michael,
what do you mean with "cleaning it"?
rm -r ~/.m2
and then rebuild the project we are using (whereas all libs and poms
were downloaded again via ant+maven)
How did you made it to work with FOP
0.94 or 0.93 without jimi?
as said it was kind of strange, because after the "clean" from above the
error message didn't show anymore.
I guess it's a classpath problem, where some other lib was used first,
but which was outdated somehow.
HTH
Michael
Thanks,
kaspersky
Michael Wechner wrote:
Chris Bowditch wrote:
Jeremias Maerki wrote:
<snip/>
So if FOP does want Jimi, putting it in the classpath hopefully fixes
the problem. But still, I'm at a loss to explain why the JimiImage class
is triggered in the first place.
The Original Post said FOP had been built via Maven. So could it be
that the FOP Maven POM has an incorrect dependency on Jimi?
I didn't see any for FOP-0.93
The code of FOP-0.93 itself is calling Jimi during runtime via dynamic
class loading, and hence one will not notice the missing Jimi lib until
actually running it.
But as said, after cleaning it's working now fine (which is strange
though ;-)
Cheers
Michael
<snip/>
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Yanel, Yulup
http://www.wyona.com
[EMAIL PROTECTED], [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Yanel, Yulup
http://www.wyona.com
[EMAIL PROTECTED], [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
