On Sat, Sep 13, 2008 at 9:52 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: >> >> On Wed, Sep 10, 2008 at 10:45 PM, <[EMAIL PROTECTED]> wrote: >>> >>> Author: bago >>> Date: Wed Sep 10 14:45:58 2008 >>> New Revision: 694009 >>> >>> URL: http://svn.apache.org/viewvc?rev=694009&view=rev >>> Log: >>> Include imap jars while building. They are a dependency like anything >>> else from stage. >> >> one of my aims was to prevent general modules coupling to IMAP >> directly. IMAP should really be a component deployed within pheonix or >> spring. that's not really possible ATM but should be possible in the >> medium term. i would strongly prefer no modules (other than >> imap-function) to reference code from IMAP. > > I don't know the ant build enough to understand how to declare a dependency > for a function that is inherited by the deployments. > > Imap jars are the same identical thing as > ${mstor.jar} > ${xstream.jar} > ${torque.jar} > ${village.jar} > ${jackrabbit-api.jar} > ${jackrabbit-commons.jar} > ${jackrabbit-rmi.jar} > ${jcr.jar} > ${spring.jar} > ${log4j.jar} > ${avalon-phoenix.jar} > ${activemq-core.jar} > ${jms-spec.jar} > > Given that we have all of them in common-build.xml I thought also imap jars > belong to that file.
some (or many) are in there for historic reasons. > It would be cool if we had a maven like way to declare local dependencies in > functions and have them transitively added to the deployment. it is perfectly possible but i want to work in categories since a large purpose is to illuminate the coupling in james server so that it can be fixed. there are some wider and deeper issues so i'll probably pick this up in a different thread... - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
