Lines Matching +full:build +full:- +full:system
1 ---
3 title: Release Build
7 ---
9 <!--
12 -->
14 # Release Build
18 {: .no_toc .text-delta }
23 ---
29 supports JRE 7 or later Java runtime environment. To avoid the Java's system
31 compiled with Java system libraries from JRE 7.*</span>
36 * Java Runtime Environment 7 (used as bootclasspath for cross-compilation)
43 * Maven Ant Tasks 2.1.3 (GA only) \[<http://maven.apache.org/ant-tasks>\]
47 * ICU Project PGP key (icuintl@us.ibm.com - [published to MIT key
51 Guide](http://central.sonatype.org/pages/ossrh-guide.html))
62 * See `build.properties` to check version strings are properly set.
65 * `release.file.ver` is used as a part of build output file name.
79 * Create `build-local.properties` in the ICU4J root directory
81 * Edit `build-local.properties` to add a property - `java7.bootclasspath
84 The value of javaX.bootclasspath should include JRE's system library path. A
85 set of jar files included in the system library path may vary depending on
87 The easiest way to get the system library path is to run a simple Java
90 System.out.println(System.getProperty("sun.boot.class.path"));
92 For example, the values on my Linux system (Ubuntu) look like below:
96 One Windows system, path separator back slash '\\' should be replaced with
103 * Add 2 more properties to `build-local.properties`
104 * `maven-ant-tasks.jar` - Specify the path to the Maven Ant Tasks jar
106 * `gpg.user` - Specify the ICU Project PGP key user name
108 For example, build-local.properties look like below:
112 maven-ant-tasks.jar = /home/yoshito/java-libs/maven-ant-tasks/maven-ant-tasks-2.1.3.jar
116 …blish ICU artifacts to the repository (ticket [ICU-12811](https://unicode-org.atlassian.net/browse…
125 <id>icu4j-releases</id>
127 <password>OSSRH-SonaType-Password</password>
130 <id>icu4j-snapshots</id>
132 <password>OSSRH-SonaType-Password</password>
140 1. Checkout tagged version - Use clean checkout of Git (SVN up to ICU62) tag
141 (e.g. release-61-0-1, release-61-rc..) for building release files.
142 2. Run `$ ant releaseVer` - This build target generates ICU release files with
145 This ant target prints out warning messages as below if the build system is
150 [echo] [WARNING] Insufficient Build Configuration for ICU4J Release
152 [echo] JRE 7 System Library Path: Not Defined!
153 …-libs/jcite-1.13.0/build/jcite.jar:/home/yoshito/java-libs/jcite-1.13.0/lib/commons-discovery-0.4.…
156 BUILD SUCCESSFUL
159 If you see such warnings at the end of build log, fix the issue and run the
166 as well as the ICU project site. The build target `releaseFinal` generates all
168 build target is executed.
169 1. Checkout tagged version - Use clean checkout of Git (SVN up to ICU62) tag
170 (e.g. release-61-1, release-61-2) for building release files.
171 2. Run `$ ant releaseVer` once to make sure there are no build configuration
172 issues. Run `$ ant clean` to clean up build.
173 3. \[Optional\] In the next step, the build target invokes gpg to generate
174 signature of build output files. gpg will request you to type in the
178 would want to run gpg-agent to cache passphrase. More specifically, once you
179 set up gpg-agent, run `$ gpg -ab -u "ICU Project" foo.txt` to sign arbitrary
185 staging repository. You should see build log as below at the end.
187 [deploy] Transferring 37K from icu4j-releases
189 …[deploy] Uploading: com/ibm/icu/icu4j-localespi/61.1/icu4j-localespi-61.1-sources.jar.asc to repos…
190 [deploy] Transferring 0K from icu4j-releases
192 …[deploy] Uploading: com/ibm/icu/icu4j-localespi/61.1/icu4j-localespi-61.1-javadoc.jar to repositor…
193 [deploy] Transferring 22K from icu4j-releases
195 …[deploy] Uploading: com/ibm/icu/icu4j-localespi/61.1/icu4j-localespi-61.1-javadoc.jar.asc to repos…
196 [deploy] Transferring 0K from icu4j-releases
199 BUILD SUCCESSFUL
205 "Staging Repositories" under "Build Promotion" on the left navigation pane,