[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [pdt-dev] All-in-one packaging for PDT 2.0 (incorporated into commonbuilder)
- From: "Roy Ganor" <roy@xxxxxxxx>
- Date: Tue, 9 Dec 2008 08:44:48 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: AclZw30k3q89LPMZTy2XKiuRNaVv1AAAW/rw
- Thread-topic: [pdt-dev] All-in-one packaging for PDT 2.0 (incorporated into commonbuilder)
These are great news! Especially for people who are having troubles
composing their Eclipse PDT environment (PHP developers are new to the
Anyway, two questions about this package:
1. Do you tag the PDT plug-ins (org.eclipse.php.*) before building it?
In most cases we should track S and R releases to have the ability to
fix critical issues on a specific release.
2. the dependencies list that is used in the modeling/pdt mechanism is
looser than what we are used to. So comparing to the 100MB bundle (ok
it's also runtime) we now get some other plug-ins that PHP developers
are not likely to use (*.jsp.* ;)).
Anyway we are going to start testing this release today. Unless there
are critical issues with our new features we will release it this
Thanks for pushing forward this process! This is much appreciated!
From: pdt-dev-bounces@xxxxxxxxxxx [mailto:pdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Nick Boldt
Sent: Tuesday, December 09, 2008 8:00 AM
To: PDT Developers
Subject: [pdt-dev] All-in-one packaging for PDT 2.0 (incorporated into
I've managed to add all-in-one packaging to the common build system; it
will currently run for win32, macosx-carbon and linux-gtk, if the build
type is S or R. Bundles are about 282M each, as they include all the
deps fed into the build (including WTP, DTP, and DLTK SDKs). This could
be made leaner by feeding in runtimes instead of SDKs; the idea was to
bundle up the same reqs used in the build into all-in-one zips.
It still needs testing -- specifically, the linux tar.gz seems
to not have the correct executable bit set for the ./eclipse executable,
and I need to verify that dumping everything into dropins/ will work out
of the box (that is, the features/plugins will all be found and run).
If you'd like to give it a test, there's a few builds on
modeling.eclipse.org you can try -- these are of course not yet the
Official PDT 2.0.0RC1 builds, just candidate test-builds toward that
Nick Boldt :: JBoss, a division of Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash CBI
pdt-dev mailing list