On Fri, Oct 31, 2008 at 8:17 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: >> http://svn.apache.org/repos/asf/james/server/trunk/javamail-util/src/main/java/org/apache/james/util/mail/mdn/ >> contains a nice little library for content disposition. ATM this seems >> to be used only by the sieve mailet >> (http://svn.apache.org/repos/asf/james/server/trunk/spoolmanager-function/src/main/java/org/apache/james/transport/mailets/sieve/). >> i'd like to move the sieve mailet from the main james distribution to >> become a module of jsieve >> (http://svn.apache.org/repos/asf/james/jsieve/trunk/) but this means >> decoupling or moving it's dependencies. i think i can sort of most of >> them but the MDN library would be difficult to replace. given that >> it's not used anywhere else in James, i'd prefer to repackage and move >> it into a library. perhaps it might be reviewed for inclusion in >> mime4j but for now i'd like to move it with the sieve mailet. >> >> opinions? > > the MDN library is bound to javamail ATM, so mime4j is not the place.
that was also my general opinion but we can review when it's factored out >> anyone know of any reasons not to move the MDN library with the mailet? > > no, but take care of the "mailcap" in the process. IIRC it contains MDN > related configuration and should be moved where the MDN classes are. mailcap a bit of a PITA: it restricts good modularity - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
