RepositoryLayout

Repository Layout

This describes the proposed repository layout as implemented in the Mercurial repository css-repo-strawman (browseable at http://cs-studio.hg.sourceforge.net/hgweb/cs-studio/css-repo-strawman/file/7bd356de94ac )

root
  |-- applications     // Contains all the sources for the application layer. No code in core should depend on these plugins
  |      |-- features  // Contains the features of the application layer. A features is a pure collection of plugins
  |      |-- plugins   // Contains all the plugins of the application layer.
  |-- build // Contains all the build scripts. The build creates temporary directory, which are ignored by the repository
  |-- core  // Contains all the sources for the core layers. No code in core should depend on anything else
  |      |-- plugins   // Contains all the plugins of core.
  |-- products // Contains all the targets of the build system. Each subdirectory contains the conf files, features and plugins specific for each product
         |-- nsls2
         |     |-- features
         |     |-- plugins
         |     |-- build.properties
         |     |-- other site specific files
         |-- sns
         |-- ...

Plugins and features within layer are not subdivided in further directory. This makes it easier in Eclipse to open all the dependencies and to split/merge plugins without disrupting the developers and the build excessively. One can than use standard eclipse functionality (working sets, open dependencies, ...) to easily hide all the extra plugin.