Since I making incompatible changes to the deployer api which means updating virtual all users of the api, I decided to do some "Dillionism" and restructure the project into 4 areas. This is really more than just "Dillionism" because it makes people think about where and how they implement things. The structure is broken down as follows: * Core - These are datastructures and helpers that are useful in all the projects. * Client - The client side api - this is intended to be used outside jboss * Structure - The core infrastructure for the structural deployers - it also defines the core datastructures used by the deployers * SPI/Impl - This is the deployers and MainDeployer * VFS - VFS extensions to the above, see the later post on why the VFS is seperated Some quick comments: * Most of the projects are seperated into spi/impl, e.g. deployers-client and deployers-client-spi The one exception is the structure project. Since the only implementation of the structure is via the VFS, the implementation of this spi is actually in the deployer-vfs project * The core api defines the StructureMetaData. I don't really like this being here, but it is used by the client side api. As such, we can't really have things from the server side leaking into this code, so I didn't want to put it into the structure project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058749#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...