[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [wtp-dev] Moving to M6 based development
|
Jeff,
Each build cleans itself after the build completes, so it probably
deleted the files it has built. On the build machine this is not an
issue because they are uploaded before cealunup:
build.home - Build root (you must be setting this before running
the buid to a place like c:\mybuilds)
build.home/build-current-N is where the current build takes
place
build.home/build-current-N/workdir/N-N2005..... is where the
artifacts of your current build are
build.home/publish - is where your artifacts are copied before the
build-current-N is deleted
These are the places you should look:
Each build At 12:31 PM 4/3/2005, Jeffrey Liu wrote:
Hi Naci,
My local N build ran to completion, however, I can't find the wtp zip files (ex. wtp-N20050403.zip) anywhere. Can you shed some light on where the zip files might be?
Thanks,
Jeffrey Liu
IBM Rational Software - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
jeffliu@xxxxxxxxxx
Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx
04/02/2005 10:57 PM
Please respond to
"General discussion of project-wide or architectural issues."
To
wtp-dev@xxxxxxxxxxx
cc
Subject
Re: [wtp-dev] Moving to M6 based development
This also has some remifications on the builds. The generated build.scripts has an "archived" property that exists after M6 release. releng.basebuilder is not updated with it yet. We changed the build-driver so that it uses the new pde.build plugin.
If you re doing local builds, please move to M6 to drive your builds.
At 05:39 AM 4/3/2005, David M Williams wrote:
In case others don't know (I follow eclipse.dev and still had to verify with platform team) ...
When using M6 in a target, you will *have* to move up to a development environment based on M6.
This is so the development environment (PDE) can correctly handle the new "jarred plugins" the base is moving to.
AFAIK, existing workspaces should be fine to point the new environment to.
BTW, as we learned (suffered through) last release, forward compatibility from milestone to milestone is never guaranteed, we've just been lucky it usually works.
Thanks
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
Naci Dai,
Managing Director
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (532) 573 7783 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
Naci Dai,
Managing Director
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 81090
+90 (532) 573 7783 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx