We have a project in SVN that is made of several projects, something like this:
- core - core project - common - common libraries - pluginA - pluginB ... etc - doc - for documentation) - tools - some command line tools - dist - distribution project which packages all of the above projects into one or more packages (RPM:s for instance) Most of the the projects generate jar:s, but some generate EAR:s. Now on one hand we could create a main project with modules, but that ties the modules so tightly to the main project, or? And the plugins (and future plugins) we would like to be able to give to third-party resources etc and they should not have access to most core sources etc Additionally, if we put modules in subdirectories in SVN (as recommended) it becomes more awkward to release separate versions of the modules? At the end it should be easy to build the whole project and package it, for instance automatically from within continuum for instance. Additionally, for developers it should be easy to check out all projects automatically and recursively into Eclipse... Any suggestions about the best strategy for a project like this? //Kent
