Hi Stefan,
On 09/06/2016 09:10 PM, Stefan Xenos wrote:
...things don't install properly because there's stuff in the Eclipse
for Committers package that isn't included in the 4.7 I-build. This is
especially problematic because the UI setup page instructions tell
users to start by installing Eclipse for Committers:
https://wiki.eclipse.org/Platform_UI/How_to_Contribute
...so if anyone follows these instructions, they aren't actually using
an I-build and don't have an easy way to change their environment to
do so. This also seems to be a problem with all Oomph-installed
versions of Eclipse. Since Oomph uses these Eclipse packages as the
basis for all of its installations, there doesn't seem to be a way to
use Oomph and an Eclipse 4.7 I-build at the same time, which is a real
problem. I've described it in more detail here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=500481
It's not a matter of content, but a matter of stream: Platform
recommends to use the currently developed stream, and packages are on
the last released one.
Many Eclipse committers are happy to rely on the last released version,
and this is totally fine for the majority of the Eclipse.org projects.
Platform UI is the only one that mostly require to work with a recent
SDK of the same stream.
1. Delete the "Eclipse for Committers" package entirely. Recommend
that commiters install the "Eclipse Platform" build (or whatever
package it is that builds
http://download.eclipse.org/eclipse/updates/4.7-I-builds/ ). Update
the oomph scripts to install any extra stuff as part of the oomph
install script rather than as part of the package.
IMHO, that would make sense. Especially since there is an "Eclipse for
RCP/RAP developers" which contains a super-content of the "Eclipse for
Committers" one (and no, RAP isn't affecting badly UI nor performance as
some thought in the past).
The "Eclipse for Committers" is indeed a bad name for Platform, because
it seems to be the standard package for committers, whereas it's
actually not the one that works for Platform.
2. Keep "Eclipse for Committers" package, but reduce its contents such
that it contains exactly those plugins that we produce integration
builds for. Update the Oomph scripts to install any extra stuff as
part of the install script.
See above, I don't think it's a matter of content, but a matter of
versions and stream. So I'm afraid that solution wouldn't work.
3. Keep the current "Eclipse for Committers" package with its current
contents and start running integration builds for it.
EPP packages are built on any SimRel change, so what you're asking for
here is supposed to be available at
https://hudson.eclipse.org/packaging/job/oxygen.epp-tycho-build/ (when
there is a good build available).
Maybe the Platform doc can be updated to recommend using such
integration build.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
