Changes between Version 42 and Version 43 of BuildSystem


Ignore:
Timestamp:
12/14/12 22:47:57 (7 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildSystem

    v42 v43  
    2525  - Projects import and export class code and data in the form of jar or zip files. Whenever viable, there is no sharing of source code (one exception is C++ code in Linux, which typically has to be recompiled on each system). This ensures that every project can be built stand alone, after importing the necessary library files. 
    2626 
     27 
     28== Why dependency management == 
     29The contents of lib directories consists of jar les and/or \dll" or \so" les 
     30that are necessary for compiling and running the project. The basic strategy 
     31is that inter-dependencies between projects are via import/export of library 
     32jar files, in preference over direct source code dependencies. Of course we 
     33have to face the problem of project versioning. We have stable release versions 
     34of projects, but also less stable daily releases and alpha versions. Here we have some 
     35conventions and rules. For instance, we do not want a stable release version 
     36of project X to be dependent on an unstable alpha version of project Y. The 
     37other way around, so an alpha version of X dependent on a release version of Y 
     38is OK of course. It will be clear that manual version management is not a good idea: lot's of work,  
     39and error prone. Instead, we use a dependency manager, 
     40[Ivy|http://ant.apache.org/ivy/]. 
    2741 
    2842