IMHO, if the committer are not using it (and it seems, so far most
dont want to), the profile is very likely to get outdated. We had
the same situation in other projects. Additionally the profile then
usually misses some fancy configurations, most committers are aware
of.
When we started to use it all internaly in other projects, we
started to manage a always working profile. Actually, it saves a lot
of effort, as it not only helps with the initial set up, but also
allows to update the IDE.
I am not saying, we can force anyone to use it, however, if it
works, it should be one click to start to use it...
Just my two cents...
Am 08.03.2016 um 15:00 schrieb Stefan
Xenos:
> Also, Oomph is
very useful when bootstrapping the IDE to contribute to a
project; once the IDE is set up, there is not much reason to
wipe it out and try again the Oomph installer.
Actually, Oomph seems useful
for more than just bootstrapping. They also have an update
command in the help menu that pulls in updates to the
configuration. We can use this whenever platform UI adds a
new required plugin or source dependency to make sure all
developers receive the new dependency without getting
compiler errors. It also checks for configurations changes
on restart, so any committer using oomph will automatically
pull in project configuration changes every time they
update.
You can also use it if you -
for example - want to contribute to another project - such
as SWT, JDT, or CDT, to update your environment with the
union of the features you'll need. They also have things like dynamic
working sets that will track the contents of the platform UI
repository and a more robust target platform specification
that will be less likely to produce workspace errors
(there's a fair number of error scenarios that Oomph can
handle and a target platform definition can't). So there's
some very useful things that oomph does that are unrelated
to initial setup.
> -1 for requiring everyone to use
it, we should allow also the old flow
I'm fine with allowing it,
but we shouldn't post both sets of instructions since that's
confusing to new users. We also shouldn't be maintaining
both the .psf + installer configuration files along with an
oomph configuration, when the oomph configuration is
superior.
- Stefan
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
--
Dr. Jonas Helming
Senior Software Architect / General Manager
EclipseSource Munich
Email: jhelming@xxxxxxxxxxxxxxxxx
Web: http://eclipsesource.com/munich
Phone: +49 89 21 555 30 - 11
Mobile: +49 170 31 51 698
Fax: +49 89 21 555 30 - 19
Skype: jonas.helming
EclipseSource Muenchen GmbH
Agnes-Pockels-Bogen 1
80992 Muenchen
General Managers: Dr. Jonas Helming, Dr. Maximilian Koegel
Registered Office: Agnes-Pockels-Bogen 1, 80992 Muenchen,
Commercial Register Muenchen, HRB 191789
|