Then all is fine. We are allowed to compile against jimi, but we must not provide it in our binary distribution ( -> <scope>provided</scope> ).
Best is to check for the absence of jimi with Class.forName() or likewise, and just don't provide image manipulation features if its not present. But for what I've seen this is already done this way, isn't? LieGrue, strub --- On Sat, 4/23/11, Dan Haywood <[email protected]> wrote: > From: Dan Haywood <[email protected]> > Subject: Re: thinking about a release > To: [email protected] > Date: Saturday, April 23, 2011, 9:44 PM > > On 23/04/2011 21:57, Siegfried Goeschl wrote: > > > > Is Jimi a mandatory or an optional dependency? > It's a built-time only dependency; it's used by the > maven-docbkx-plugin > to generate our PDFs and HTML. > > There's no need for anyone using Isis to install JIMI > manually or otherwise. > > Is that ok? else what advice for us? > > Thanks > Dan > >
