Hi Robert, I see you already noticed the move was not pleasing... but... can you explain why we need to move an api for our core library in an imap package?
I would avoid to move core stuff in imap dependencies at all as imap should be optional. If this is only a limit of the ant build (the api-library-function-deployment layer) I would prefer to introduce another layer or an hack (like I did for the mailet-api in past) in the build system instead of having such a dependency on imap-api for the whole project. My concern are related to the "long run". If this is few weeks then ignore my comment, otherwise we should find a different solution. Stefano [EMAIL PROTECTED] ha scritto: > Author: rdonkin > Date: Mon Jun 11 13:43:28 2007 > New Revision: 546266 > > URL: http://svn.apache.org/viewvc?view=rev&rev=546266 > Log: > This move is not particularly pleasing :-/ Hopefully in the long run, a more > elegant solution will be found but this is necessary before the refactoring > and modularisation can be completed which will allow the code on the branch > to be merged in. > > Added: > james/server/trunk/imap-api/src/main/java/org/apache/james/services/ > > james/server/trunk/imap-api/src/main/java/org/apache/james/services/User.java > - copied unchanged from r546261, > james/server/trunk/core-library/src/main/java/org/apache/james/services/User.java > Removed: > > james/server/trunk/core-library/src/main/java/org/apache/james/services/User.java --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
