Confirming what Roman said, it's part of the bundle. Sometimes modules do require other libraries to operate, but installing those libraries is as simple as copy/paste the JAR into the same lib directory I mentioned before.
Do not simply copy [i]all[/i] of the JARs from a bundle into the lib directory, though. Sometimes you'll get a secondary (or older) version of a library that's already in there. For example, if the shop bundle contains magnolia-module-dms-1.6.1.jar then you may also have magnolia-module-dms-1.6.5 already in that lib directory. By having 2 version of the same thing, your instance of magnolia will fail to deploy because of a classpath conflict. You [u]do[/u] have to copy any dependencies (like OCM) to both webapps magnoliaAuthor and magnoliaPublic, just like with the one you already installed. Good luck. :) -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=bfcfeba5-1092-44bc-a183-3ef4b930a1c1 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
