Project

General

Profile

How to Build z2 Base » History » Version 2

Henning Blohm, 14.09.2021 12:47

1 1 Henning Blohm
h1. How to Build z2 Base
2
3
Starting with z2 v2.6 the z2-Environment comes as a completely self-contained package containing the z2-base components (in particular including Jetty) so that you do not need to setup online copies of z2-base.base unless you plan on patching those components regularly.
4
5
In order to build the distribution all you need is
6
7
* The required min. Java version (see [[Java Version Requirements]])
8
* A somewhat up-to-date ANT installation (see https://ant.apache.org/)
9
10
11
In order to build and try out for development create a workspace somewhere and
12
13
h3. 1. Clone z2-core
14
15
<pre><code class="bash">
16
git clone https://www.z2-environment.net/git/z2-core
17
</code></pre>
18
19
Note:
20
21
* If you do not want to build @master@ switch branches accordingly.
22
* The build will clone the @z2-base.base@ to include it in the distribution. Before packaging, the build will attempt to checkout the same branch (by name) that is checked out in @z2-core@
23
24
h3. 2. Build
25
26
Run
27
28
<pre><code class="bash">
29
cd z2-core/package
30
ant
31
</code></pre>
32
33
After that: 
34
35
* A fresh distribution is at @gen/dist@
36
37
h3. 3. Run
38
39
You can start the just build distribution by running
40
41
<pre><code class="bash">
42
./gui.sh
43
</code></pre>
44
45 2 Henning Blohm
However, if you need to frequently rebuild and want to test or develop with other modules located "next" to your z2-core checkout, 
46
you may want to start using the @gui.sh@ or @go.sh@ scripts located in @z2-core/package@ rather than the ones of the built output.
47
48
These scripts overwrite the default location of the development workspace to be "next to z2-core".
49
50 1 Henning Blohm
h3. 4. Alternative Builds for Distribution
51
52
If you want to build an archive, run either
53
54
<pre><code class="bash">
55
ant build_release_candidate
56
</code></pre>
57
58
to create an archive whose name contains the branch name and a timestamp or
59
60
<pre><code class="bash">
61
ant build_release
62
</code></pre>
63
64
to create an archive whose name contains the branch name.