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? Thanks. On 10/24/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
This isn't a recommended project structure. Attachments (that's what we call it) do exist though, for instance for an ejb project (the ejb-jar is the main jar, and there's an ejb-client jar with just the interfaces). If you separate the api and the impl, there must be a reason for it, like supporting multiple impls. In that case I'd recommend splitting the project up. Even if you distribute the api classes to a client and keep the impl on a server, it's worth separating the projects. -- Kenney -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
