On Mon, 2005-10-24 at 15:18 -0700, Meg Hsu wrote: > Hi Kenney, > Thanks for your input. The reason we have such structure is to > eliminate the situation where the impl classes have references to > other impl classes instead of api classes in other sub-projects. > So at compile time, only the api jars will be used. > The purpose is to reduce the impact when the impl is changed > in some sub-projects. > Right now we have 14 sub-projects. If break them up, there will > be 28 projects.. Or we need to consolidate some of our projects. > Is the Attachments a plug-in? Do you know where I can find more > info about it?
Another alternative is to put the APIs in one single project which is ok if this is a single application. That way you won't have components using other components directly and still have a manageable set of projects. -- Trygve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
