Changes between Version 34 and Version 35 of BuildSystem


Ignore:
Timestamp:
12/04/12 17:09:34 (7 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildSystem

    v34 v35  
    1515agree on a number of basic conventions and procedures. 
    1616 
    17 * We do not assume that everyone will be using the same development 
    18 toolkit or any toolkit at all. But we do require that a project created 
    19 and developed, say, by means of Netbeans or Eclipse, can be (re)build 
    20 without any of these tools available. 
    21  
    22 * Since we have to use some common build tool, we have agreed to use ant 
    23 as that “common” minimal platform. 
    24  
    25 * In principle every project lives in its own directory, containing all relevant 
    26 source code, test code, project specific data, library files needed by that 
    27 project, project documentation, etcetera. We have a preferred standard 
    28 layout for the directory structure inside a project. A project also contains 
    29 an ant buildfile (build.xml) and usually also a build.properties file. 
    30 We require that we can (re)build and run a project using ant, without 
    31 any reliance on development tools that might have been used to develop 
    32 the project. To be clear: we don’t want to install JBuilder or Netbeans 
    33 or Eclipse or whatever just to build and run your project. The ant file 
    34 can be either a simple “standalone” build file, but the preferred way is 
    35 to use a very small build file that just links to our shared build file. (See 
    36 below) 
     17* We do not assume that everyone will be using the same development toolkit or any toolkit at all. But we do require that a project created and developed, say, by means of Netbeans or Eclipse, can be (re)build without any of these tools available. 
     18 
     19* Since we have to use some common build tool, we have agreed to use ant as that “common” minimal platform. 
     20 
     21* In principle every project lives in its own directory, containing all relevant source code, test code, project specific data, library files needed by that project, project documentation, etcetera. We have a preferred standard layout for the directory structure inside a project. A project also contains an ant buildfile (build.xml) and usually also a build.properties file. We require that we can (re)build and run a project using ant, without any reliance on development tools that might have been used to develop the project. To be clear: we don’t want to install JBuilder or Netbeans or Eclipse or whatever just to build and run your project. The ant file can be either a simple “standalone” build file, but the preferred way is to use a very small build file that just links to our shared build file. (See below) 
    3722 
    3823* We have a limited number of shared projects, all of which are available from our GIT repositories: