Changes between Version 45 and Version 46 of BuildSystem


Ignore:
Timestamp:
12/14/12 22:55:31 (7 years ago)
Author:
welberge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildSystem

    v45 v46  
    4141 
    4242=== How does it work? === 
    43 Every project has an "ivy.xml" file that describes project dependencies. The 
    44 ant build files, relying on the Ivy system, use these so called "ivy's" for resolving 
     43Every project has an "ivy.xml" file that describes project dependencies. The 
     44ant build files, relying on the Ivy system, use these so called "ivy's" for resolving 
    4545the contents of the project's lib directory. The system is based upon the 
    46 notion of configurations, versions, and status of versions. For example, our 
     46notion of configurations, versions, and status of versions. For example, our 
    4747build system uses "alpha", "daily build", and "release" as possible status of some 
    4848jar version. The ordering of these statuses is relevant. For instance, when you 
     
    5050published daily releases and release (but not alpha) versions of that module. Similarly, if 
    5151you ask for a "latest alpha", anything is acceptable, but if you ask for a "latest 
    52 release", then only versions classified as "release" are taken into consideration. 
    53 Ivy allows for several "configurations" of the project, each with its own set 
    54 of dependencies. Currently, we have configurations for producing alpha, daily build, 
    55 and release versions of the project itself, and a "test" configuration for (extra) 
     52release", then only versions classified as "release" are taken into consideration. 
     53Ivy allows for several "configurations" of the project, each with its own set 
     54of dependencies. Currently, we have configurations for producing alpha, daily build, 
     55and release versions of the project itself, and a "test" configuration for (extra) 
    5656dependencies needed for running tests. (For technical reasons we have two more 
    57 configurations, called \master" and \default", which are discussed below) The 
    58 workflow is roughly as follows: first move the project into either the alpha, 
    59 beta or release configuration, second do your development, including testing 
     57configurations, called \master" and \default", which are discussed below) The 
     58workflow is roughly as follows: first move the project into either the alpha, 
     59beta or release configuration, second do your development, including testing 
    6060etc, third publish an alpha, beta or normal release based upon the current 
    61 configuration. When you actually publish, we attach a version number to the 
    62 jar file. Also, the Ivy system records metadata concerning published modules 
     61configuration. When you actually publish, we attach a version number to the 
     62jar file. Also, the Ivy system records metadata concerning published modules 
    6363based upon version numbers, to be used later on, when resolving for other 
    64 projects. It does so by publishing not just a "jar" file (or other "artefacts", as 
    65 they are called by Ivy), but also an accompanying ivy.xml file, derived from 
     64projects. It does so by publishing not just a "jar" file (or other "artifacts", as 
     65they are called by Ivy), but also an accompanying ivy.xml file, derived from 
    6666the project's ivy at the moment of publication. In this way, the Ivy system 
    6767knows not only about direct dependencies, but is also capable of resolving 
    6868recursive dependencies. This means that, for instance, when my module X 
    69 declares (just) a dependency on the HmiGraphics package, the resolve process 
    70 will look into the dependencies of HmiGraphics. The result is that project 
    71 X will receive jar files for HmiGraphics, but also for HmiAnimation, HmiXml, 
     69declares (just) a dependency on the !HmiGraphics package, the resolve process 
     70will look into the dependencies of !HmiGraphics. The result is that project 
     71X will receive jar files for !HmiGraphics, but also for !HmiAnimation, !HmiXml, 
    7272HmiMath, and HmiUtil, because of (recursive) dependencies. When some jar 
    73 file is required more than once, say via a direct dependency and also via some 
     73file is required more than once, say via a direct dependency and also via some 
    7474indirect dependency, and the versions required are not consistent, then Ivy 
    7575delivers the "latest" version. So, for instance, in the example above, if project 
    76 X declares (direct) dependencies on the alpha version of HmiGraphics and the 
    77 release version of HmiXml, while the alpha version of HmiGraphics declares itself 
    78 a dependency on the beta version of HmiXml, then project X will receive that 
    79 beta version of HmiXml. That should be ok: since we are asking for some alpha 
    80 version (of HmiGraphics, we should allow other alpha and/or beta versions if 
    81 HmiGraphics actually needs them, even if our own project would be satisfied 
     76X declares (direct) dependencies on the alpha version of !HmiGraphics and the 
     77release version of !HmiXml, while the alpha version of !HmiGraphics declares itself 
     78a dependency on the beta version of !HmiXml, then project X will receive that 
     79beta version of !HmiXml. That should be ok: since we are asking for some alpha 
     80version (of !HmiGraphics, we should allow other alpha and/or beta versions if 
     81!HmiGraphics actually needs them, even if our own project would be satisfied 
    8282with the most recent release version. 
    8383