[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
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
