A small set of Eclipse Platform bundles
have been forked in the 4.0 stream. Their version numbers vary depending
on what has changed in them. You can upgrade from a 3.6 build to a 4.0
build, but not vice-versa (it's a one way trip). A given version of org.eclipse.sdk
feature "locks" a precise version of the Platform/JDT/PDE features,
so you can't mix and match them if you have the 4.0 SDK installed. If you
install the 4.0 stream platform runtime binary build, you should be able
to pick up different versions of PDE and JDT. In general, since the 4.0
stream build is picking up most of the bundles directly from the 3.6 stream
build, there is no reason to do this.
As for messaging about 4.0, we tried
to describe this in the first paragraph of the 4.0 plan. There likely won't
be many new features for an end user, apart from a new look and feel, and
perhaps more flexibility in laying out views and editors. The underlying
technology will be "1.0" level so the casual or conservative
user will likely not migrate to it. I think the simultaneous release train
remains the primary mechanism for most end users to consume Eclipse technology,
and the platform 4.0 release won't be part of the release train at all
for 2010. Of course we think there's some pretty cool stuff in here and
it does represent the long term direction of the platform, so people building
layers on top of the platform and RCP application developers should certainly
be checking out the 4.0 release. I'm sure there will be more conversations
about how to get the right word out as we get closer to the release..
Ian Bull <irbull@xxxxxxxxxxxxxxxxx> Sent by: e4-dev-bounces@xxxxxxxxxxx
04/17/2010 01:01 PM
Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
Re: [e4-dev] Eclipse Project 4.0 Release
This is very exciting, thanks for the update John!
I have two questions about this.
First, have any of the Eclipse 3.x platform bundles changed in the 4.0
SDK? If they have, what version numbers (and update descriptors)
are they using? I'm wondering if we can install Helios and "upgrade"
to the 4.0 SDK, and then use the 3.x update sites for the PDE/JDT/Platform
updates? Or, once you go to the 4.0 SDK will you be required to use
the 4.0 update sites for everything? -- Maybe it's a little too early
to try this yet.
Secondly, what should we (Eclipse committers) be telling people about Eclipse
4.0? Obviously there are lots of people who simply use Eclipse as
their IDE of choice. Are the plans to produce EPP packages for Eclipse
4.0? I imagine that when we release Eclipse 3.6 and a month later
release Eclipse 4.0, there will be some confusion among users regarding
what version they should use. From what I can tell, it appears that
there will be very few "end user features" in Eclipse 4.0.
However, I don't want to discourage people from using it if it's the intended
upgrade path (Install 3.6 and upgrade to 4.0 in July).
Again, this is awesome! I'm been following the e4 lists for at least
2 years now and it's really exciting to see all this work come together.
Congratulations to everyone involved.
For the past eight months we have been working towards a July 2010 release
tentatively called the e4 1.0 release. One of the major goals of this release
was to bring the e4 technology delivered in our July 2009 "0.9"
release up to a level of maturity and stability that we could run the Eclipse
platform and its ecosystem of plug-ins on top of it. As a community we
have been referring to this combination of the existing Eclipse platform
with e4 technology as "Eclipse 4.0".
Last week we began building the full Eclipse 4.0 SDK, and delivered it
as part of our M5 milestone. This build combines some e4 components, the
e4 compatibility layer, and the Eclipse project 3.6 SDK. With this milestone
it is time to switch emphasis from incubating e4 work to focus on graduating,
polishing, and delivering this Eclipse 4.0 SDK. Since this combined release
incorporates plug-ins from several Eclipse sub-projects, it would be incorrect
to call it an e4 release. To reflect this reality, and our primary emphasis
on the Eclipse 4.0 SDK deliverable, the Eclipse project PMC has decided
to take the following steps:
- We will no longer refer to the "e4 1.0 release" in our plans
and downloads after M5. We will instead call our July 2010 release the
"Eclipse SDK 4.0" release. This deliverable will combine components
from the Eclipse Platform, JDT, PDE, Equinox, ECF, and EMF out of the Helios
release, with the e4 components required to build the Eclipse 4.0 SDK.
- CSS Styling, Modeled Workbench, and some of the core e4 programming model
infrastructure have matured in e4 and will move into the Eclipse Platform
project prior to the July release. This new technology allows building
the Eclipse 4.0 SDK on top of it, which thus only depends on graduated
XWT, Toolkit Model, Bespin Server, and the new e4 resources work around
semantic file systems are going to remain in the e4 incubator for now.
These components have not reached the level of stability and community
required for graduation into a mature project. We will continue to evaluate
whether more components should graduate either in this release or later
releases, based on their progress and adoption.
- The e4 components that remain in the incubator will release simultaneously
with the Eclipse top-level project's 4.0 release, and will be available
in a separate release repository, much like the Helios repository and EPP
packages incorporate both incubating and mature components in a single
release. Since we intend to keep the e4 project as a perpetual incubator,
it doesn't make sense to attach a traditional version number to the incubating
e4 portion of the release. Where necessary, we will refer to the e4 incubator
portion as the "e4 July 2010" downloads (for example on the e4
downloads page). Version numbers of individual e4 plug-ins will evolve
according to the Eclipse project's standard version numbering guidelines.
- We will continue running e4 incubator builds throughout the July 2010
release cycle (and beyond). In addition we will run Eclipse project 4.0
stream builds. Until the Eclipse project Helios release is completed, we
will run these 4.0 stream builds out of the "R4_HEAD" branch
of the Eclipse project repository. Note that the vast majority of plug-ins
don't require branching, and will be consumed directly from the "R3.6"
version tag produced by the Helios release.
A draft plan of the Eclipse Project 4.0 release is now available . This
plan is quite similar to our previous e4 plan, with the same milestones
and timeline, and most of the same plan items.