forked from jbosstm/documentation
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbuild-release-pkgs.xml
212 lines (197 loc) · 9.38 KB
/
build-release-pkgs.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
<?xml version="1.0"?>
<!--
JBoss, Home of Professional Open Source
Copyright 2009, Red Hat Middleware LLC, and individual contributors
as indicated by the @author tags.
See the copyright.txt in the distribution for a
full listing of individual contributors.
This copyrighted material is made available to anyone wishing to use,
modify, copy, or redistribute it subject to the terms and conditions
of the GNU Lesser General Public License, v. 2.1.
This program is distributed in the hope that it will be useful, but WITHOUT A
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License,
v.2.1 along with this distribution; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
MA 02110-1301, USA.
(C) 2007-2009,
@author JBoss Inc. ([email protected])
-->
<!--
build-release-pkgs.xml: Utility script for building release artifacts.
Probably only useful for dev team. Everyone else should only need the
regular build.xml.
This script automates the some steps of the release build and packaging process
to reduce the opportunities for users to get it wrong. For example, it works from
a fresh svn checkout to ensure locally modified files in a dev's svn working copy
don't sneak into the release bundle.
usage:
Tag the release in svn.
or you can do a snapshot release direct from trunk, see properties below.
Check the version of JBossAS referenced in pom.xml is sane.
In general, use the oldest JBossAS release the JBossTS release is intended to support.
Update the properties section below to suit your machine.
Set JAVA_HOME to a jdk 1.6, since that's the version we currently support.
ant -f build-release-pkgs.xml dist downloads
rsync or sftp the downloads to publish to the web site (careful with the trailing '/') e.g.
rsync \-\-protocol=29 -avz 4.11.0.Final [email protected]:downloads_htdocs/blacktie/
Log in to magnolia cms at https://www.jboss.org/author, create page under blacktie/downloads
(note: 'magnolia' target below may help) then edit downloads node itself to update table in downloads.html
Update appropriate wiki pages, such as the 'which version to use' page.
http://community.jboss.org/wiki/BlackTie
Then login to https://repository.jboss.org/nexus/ and publish the artifacts.
This version only applies to the version it was downloaded with.
-->
<project name="Release Packaging" default="fail" basedir=".">
<description>
package binary + src files for upload to website and other repos.
</description>
<!-- you probably need to change these properties to suit your machine -->
<!-- uncomment the block of properties below to do a snapshot release.
you need permissions to webdav upload to the server for this to work
http://www.jboss.org/community/docs/DOC-11381 -->
<!--
<property name="svnbase" value="https://svn.jboss.org/repos/blacktie"/>
<property name="tag" value="trunk"/>
<property name="version" value="5.0.3.Final-SNAPSHOT"/>
-->
<!-- a working directory for the process. Can contain output from previous releases if you like to keep them archived locally. -->
<!--property name="workdir" location="/tmp/blacktie_releases"/-->
<!-- where to get the source -->
<property name="svnbase" value="https://svn.jboss.org/repos/blacktie/tags"/>
<!-- The tag as it appears under svnbase -->
<property name="tag" value="5_0_0_M1"/>
<!-- The file name base for the user downloadable files. Derive it from the tag -->
<property name="version" value="5.0.0.M1"/>
<!-- the location the web site content is copied to -->
<property name="downloads.dir" value="${user.home}/blacktie/filemgmt.jboss.org/downloads_htdocs/blacktie/"/>
<property name="docs.dir" value="${user.home}/blacktie/filemgmt.jboss.org/docs_htdocs/blacktie/"/>
<property name="bpa" value="centos54x64"/>
<!-- you probably don't need to change anything below here -->
<taskdef resource="net/sf/antcontrib/antlib.xml">
<classpath>
<pathelement location="./antbuildsystem/ant-contrib-1.0b3.jar"/>
</classpath>
</taskdef>
<target name="fail">
<fail message="you must specify a target"/>
</target>
<target name="all" depends="dist,downloads"/>
<target name="dist-init" unless="dist-init">
<tstamp/>
<fail message="You must set a workdir">
<condition>
<not>
<isset property="workdir"/>
</not>
</condition>
</fail>
<fail message="You must not already have a local maven cached repository to do a release build">
<condition>
<available file="repository" type="dir"/>
</condition>
</fail>
<fail message="You cannot perform a build without cleaning the old version out">
<condition>
<available file="${workdir}/${tag}" type="dir"/>
</condition>
</fail>
<mkdir dir="${workdir}"/>
<!-- pull the source code from svn -->
<exec executable="svn" dir="${workdir}">
<arg value="checkout"/>
<arg value="${svnbase}/${tag}"/>
</exec>
</target>
<target name="dist" depends="dist-init" description="build the end-user release bundles (src and binary)">
<!-- build the binary releases -->
<exec dir="${workdir}/${tag}" executable="tools/maven/bin/mvn" failonerror="true">
<arg line="clean -gs tools/maven/conf/settings.xml -Dbpa=${bpa}"/>
</exec>
<!-- package the full source release (all src tree) -->
<delete file="${workdir}/blacktie-${version}-src.zip"/>
<zip basedir="${workdir}" destfile="${workdir}/blacktie-${version}-src.zip" includes="${tag}/**" excludes="${tag}/repository/**"/>
<!-- build the binary releases -->
<exec dir="${workdir}/${tag}" executable="tools/maven/bin/mvn" failonerror="true">
<arg line="install -DskipTests -gs tools/maven/conf/settings.xml -Dbpa=${bpa}"/>
</exec>
</target>
<!-- copy the release into the downloads dir tree (http://www.jboss.org/blacktie web site content) -->
<target name="downloads" description="copy release bundles to web site content">
<fail>
<condition>
<not>
<available file="${downloads.dir}" type="dir"/>
</not>
</condition>
</fail>
<fail>
<condition>
<available file="${downloads.dir}/${version}" type="dir"/>
</condition>
</fail>
<fail>
<condition>
<not>
<available file="${docs.dir}" type="dir"/>
</not>
</condition>
</fail>
<fail>
<condition>
<available file="${docs.dir}/${version}" type="dir"/>
</condition>
</fail>
<delete dir="tmp-downloads-dir"/>
<mkdir dir="tmp-downloads-dir"/>
<mkdir dir="tmp-downloads-dir/src"/>
<mkdir dir="tmp-downloads-dir/binary"/>
<mkdir dir="tmp-downloads-dir/xsd"/>
<delete dir="tmp-docs-dir"/>
<mkdir dir="tmp-docs-dir"/>
<copy todir="tmp-downloads-dir/src">
<fileset dir="${workdir}" includes="blacktie-${version}-src.zip"/>
</copy>
<copy todir="tmp-downloads-dir/binary">
<fileset dir="${user.home}" includes="blacktie-${version}-bin.*"/>
</copy>
<copy todir="tmp-downloads-dir/xsd">
<fileset dir="${workdir}/${tag}/blacktie-xsd/src/main/xsd/">
<include name="*.xsd"/>
</fileset>
</copy>
<copy file="${workdir}/${tag}/jatmibroker-xatmi/target/jatmibroker-xatmi-${version}-javadoc.jar" todir="tmp-downloads-dir/api/jatmibroker-xatmi"/>
<copy todir="tmp-docs-dir/guides/userguide">
<fileset dir="${workdir}/${tag}/docs/userguide/target/docbook/publish/en-US/html/"/>
</copy>
<unzip src="${workdir}/${tag}/jatmibroker-xatmi/target/jatmibroker-xatmi-${version}-javadoc.jar" dest="tmp-docs-dir/api/jatmibroker"/>
<move todir="${downloads.dir}/${version}" verbose="true">
<fileset dir="tmp-downloads-dir"/>
</move>
<move todir="${docs.dir}/${version}" verbose="true">
<fileset dir="tmp-docs-dir"/>
</move>
</target>
<!-- magnolia (the cms that sits behind jboss.org/blacktie pages) is a pain. This target generates
xml for /downloads/somerelease.xml pages to ease some of the pain in publishing an upload
right click blacktie/downloads node, import from xml, then right click new node and activate.
download ordering in the rollover menu is determined by ordering the GUI - move new page as needed.
edit the 'downloads' node itself to link the new release from downloads.html, it's not automatic. -->
<target name="magnolia">
<exec executable="date" outputproperty="date">
<arg line="+'%FT%H:%M:%S.000Z'"/>
</exec>
<length property="full-src-length" file="${workdir}/blacktie-${version}-src.zip"/>
<length property="full-bin-length" file="${workdir}/blacktie-${version}-bin.zip"/>
<copy file="magnolia-release-download-page-template.xml" tofile="${workdir}/website.downloads.${version}.xml" filtering="true" overwrite="true">
<filterset>
<filter token="tag" value="${tag}"/>
<filter token="version" value="${version}"/>
<filter token="date" value="${date}"/>
<filter token="full-src-length" value="${full-src-length}"/>
<filter token="full-bin-length" value="${full-bin-length}"/>
</filterset>
</copy>
</target>
</project>