Difference between revisions of "Building tools"
From Gcube Wiki
| Line 1: | Line 1: | ||
| − | GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a Software Configuration System (a.k.a. SCM [http://en.wikipedia.org/wiki/Software_configuration_management]) is made available to developers for storing | + | GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a central Software Configuration System (a.k.a. SCM [http://en.wikipedia.org/wiki/Software_configuration_management]) is made available (see section [[Gcube subverion repository|gCube Subversion Repository]] to developers for storing source code of all gCube components. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 16:25, 12 January 2012
GCube System embraces several (hundreds) components of different types (e.g. services, portlets, libraries, plugins, testsuites). Often there exists several dependencies between those components either at build-time of at run-time or both. To face the complexity of maintaining such a large system a central Software Configuration System (a.k.a. SCM [1]) is made available (see section gCube Subversion Repository to developers for storing source code of all gCube components.
