As a general rule, it is the committers who will decide the versions of
the libraries that a build will depend on. I guess it is best anounced
and discussed on this forum beforehand. Once there is a concensus I
will update the scripts.
Regards
Deniz
Deniz Secilir wrote:
Hi Keith,
I'm planning to update them before the milestone builds. But if you
inform me beforehand, I will also update for nightly builds.
Regards
Deniz
Keith Chong wrote:
Hi Deniz,
Thanks for the update. I noticed
that the URLs in the build.cfg point to specific drivers. How often
will you update these? For example, there is a more recent XSD SDO
EMF zip (integration build I20041104).
How does the build process address
these
updates?
Regards,
Keith Chong
D3/QCS/8200/MKM
Phone: (905) 413-4370 T/L: 969-4370
e-mail: kchong@xxxxxxxxxx
Deniz
Secilir <deniz.secilir@xxxxxxxxxxxxx>
11/05/2004 02:19 AM
|
To
|
Keith
Chong/Toronto/IBM@IBMCA |
cc
|
Craig
Salter/Toronto/IBM@IBMCA |
Subject
|
Re:
Fw:
[wtp-dev] Re: Fw:
[wtp-committers] BUILD PROCESS & CALENDAR |
|
Hi Keith,
I have added GEF to build scripts.
Build process downloads the required zips by ant's get target.
<target name="getGef" unless="gef.exists">
<get src=""
dest="${localDownloads}/${gefFile}" />
</target>
You can see it in buildAll.xml.
Let me know if I can help you.
Regards
Deniz
Keith Chong wrote:
Hi Deniz,
Ok...can you do this for me. Edit build.cfg and add this URL for
the GEF SDK.
gefURL = http://download.eclipse.org/tools/gef/downloads/drops/R-3.0.1-200408311615/GEF-SDK-3.0.1.zip
Also add this too:
gefFile = GEF-SDK-3.0.1.zip
Then, edit buildAll.zip and add the unzip command (the third one
here to unzip the gefFile)
<target name="unzipEclipse" unless="eclipse.exists">
<unzip dest="${baseLocationRoot}"
src="" overwrite="true">
</unzip>
<unzip dest="${baseLocationRoot}"
src="" overwrite="true">
</unzip>
<unzip dest="${baseLocationRoot}"
src="" overwrite="true">
</unzip>
</target>
Curious, how does the build process download the required zips to the
location
specified by localDownloads?
Regards,
Keith Chong
D3/QCS/8200/MKM
Phone: (905) 413-4370 T/L: 969-4370
e-mail: kchong@xxxxxxxxxx
----- Forwarded by Keith Chong/Toronto/IBM on 11/03/2004 05:57 PM -----
Hi Deniz,
This process seems strange to me... but perhaps only because it is
different
to what we've done in the past. Is this the process the other eclipse
teams use?
thanks
Craig
Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM
Phone: (905) 413-3918 TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx
Notes: Craig Salter/Toronto/IBM@IBMCA
At 10:25 AM 11/3/2004, you wrote:
Hi Keith,
We are re to adyadd some of our plugins to the WTP builds. Can
committers
update the script files in the org.eclipse.wtp.releng plugin as well?
We
have a dependency on GEF, so we need to update the scripts to extract
the
GEF zip to the base location.
The build scripts are now updated to download
from
a URL. You can add your changes for GEF plugin ( provide URL for GEF
Build
in build.cfg file and add script for downloading and unzipping).
Or just send me the URL and I will do it for you.
Question regarding the following point in the Build Workflow for WTP
where
you say "Label your code in CVS with the .map
files labels for the Monday integration build". We're
unclear as to what this means. Are these labels already in place
prior to tagging the source files? When we commit/release a change,
the release tool should tag the source files and then update the map
file
with the appropriate tag. Does this step mean we have to do additional
tagging? Can you provide a simple example to clarify?
Here is how the workflow goes:
-On monday, releng team labels wst and jst projects from HEAD on with
the
tag for friday (i.e. v20041224 ), the milestone build ( WTP 1.0M2 ).
The label is always the date preceeded
by a "v". You do not have to anything for this.
-Developers decide which label goes to the build by editing their
corresponding
plugin/feature in a .map file. By default we will move them to the
current lane on Monday. If anybody prefers a different label to be
used, we need to be notified.
>From this point on, committers will decide what will be gone for
Friday's
milestone build by moving the label. For the two integration builds
on monday and wednesday with the current label (v20041224).
Committers are responsible for following these builds and solving build
problems by moving their labels. Release tool will not label any file.
It uses the release which is defined in map files.
Also, are the current *.map files final/set? Should we split the
wst.map file into separate map files based on subcomponents? I noticed
jdt has jdtcore.map, jdtdebug.map, jdtui.map files.
You can split map files on subcomponents. We use all *.map files in
maps
folder so there is no problem in splitting them.
Thanks
Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com
--
Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com
--
Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com
--
Deniz Secilir
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (505) 361 25 82 (cell)
+90 (216) 361 5434 (phone)
http://www.eteration.com
|