Re: [epp-dev] oomph "bug" in EPP

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Thanks, Eike, I know that this is not a "bug" in Oomph but it occurs in relation with Oomph which is why your insight and opinion is important here.

I'm sorry, but I'm on the run and will be offline for a few hours. I hope to get more opinions from other package maintainers in the meantime, even on a Friday (evening).

Thanks,

Markus

On 19 June 2015 at 18:47, Eike Stepper <stepper@xxxxxxxxxx> wrote:

Am 19.06.2015 um 17:52 schrieb Markus Knauer:

Thanks, Max, for bringing this forward as requested!

I'd like to get more feedback from the other package maintainers whether you see this as a problem in your package, and I hope to get feedback from the Oomph team.

I'm not sure what kind of feedback is expected from us. I know it doesn't make a difference for you but this is not a bug in Oomph; it works as designed.

Oomph provides a very powerful and flexible task execution engine, which is able to install IDEs (during the "bootstrap" trigger) and update them later (during the "startup" trigger). The automatic task execution at startup time is configurable per workspace via the Oomph | Setup preferences.

In addition to (i.e. on top of) this engine Oomph provides a preference recorder that automatically creates PreferenceTasks for the preferences that are changed in the preference dialog. Once these PreferenceTasks are recorded, they get executed by the underlying setup engine at startup time (unless that is turned off as explained above). Turning off the recorder is not expected to disable already recorded preference tasks (or any other tasks).

That said, we agree that these XML blob-like preferences can become problematic because our PreferenceTasks can not change (merge) their contents selectively. We plan to come up with an enhanced infrastructure around the preference recorder that accounts for this challenge (and some other challenges such as the introduction of a machine scope in addition to the user scope). But of course that is all post-Mars music.

Technically this means we would need to add another entry to the plugin_customizations.ini  of each package that changes the default setting of the Oomph preference recorder from 'on' to 'off'. The content of the packages would be the same, the same parts of Oomph would be included and could be enabled at any time, but only through a manual change by the user. This change already found its way to the Java EE package this week. Based on this change we would have to rebuild the packages and go through another cycle with tests and votings.

Yes, that's what I thought would happen when this issue was brought up first. But apparently I was wrong ;-)

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev

--

###
EclipseSource Group
Telefon: +49 721 664733-0 (GMT +2)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany 
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883