Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 394172

Summary: Update Eclipse 4 tools projects with HandlerProcessingAddon
Product: [Eclipse Project] e4 Reporter: Marco Descher <marco>
Component: UIAssignee: Nobody - feel free to take it <nobody>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: Benjamin.Brandl, Lars.Vogel, nobody, tom.schindl
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X   
Whiteboard:
Bug Depends on:    
Bug Blocks: 396249    

Description Marco Descher CLA 2012-11-13 07:31:39 EST
According to http://www.eclipse.org/forums/index.php/m/982772 the changes for bug 376254 need to be updated within the e4 repo.
Comment 1 Lars Vogel CLA 2012-11-13 14:27:36 EST
Please use a more descriptive bug title, AFAIK this is about adding HandlerProcessingAddon in the Eclipse 4 wizard to a new project.
Comment 2 Nobody - feel free to take it CLA 2012-11-13 15:13:17 EST
I haven't thoroughly looked at the occurrences but I suppose there are other places which require attention (e.g. model editor itself like in the linked forum post etc) . The idea is that I will do a thorough search and remove for any processHierarchy references and anywhere there are the "default" addons I will add the handler addon.

@Marco, you messed up the forum post. The correct one is http://www.eclipse.org/forums/index.php/t/437480/
Comment 3 Nobody - feel free to take it CLA 2012-11-16 17:41:25 EST
Pushed fix in topic branch because I have to wait for M4 for the addon to be available on platform. If I commit to master and people get the latest tools build they would get CNF Exception because they have to have the HandlerProcessingAddon present (unless they have the latest master of platform/ui).

http://git.eclipse.org/c/e4/org.eclipse.e4.tools.git/commit/?h=smcela/HandlerAddonUpdates&id=c20a38791112a4359f4d40e5494df5874ac41d5b
Comment 4 Thomas Schindl CLA 2013-01-02 03:16:12 EST
The addon is only in 4.3M4 so what you need to do is to check if your target is 4.2.x or 4.3 and only add the addon if you are on 4.3M4!
Comment 5 Lars Vogel CLA 2013-01-02 03:18:29 EST
@Tom see Bug 396249
Comment 6 Thomas Schindl CLA 2013-01-02 03:35:41 EST
IMHO this here is a bit different. Bug 396249 talks about tooling compile time dependencies of the tooling where as here the project wizard needs to differentiate between 4.2.x and 4.3 runtimes, so it needs to check the runtime-bundles (e.g. the e4.ui.workbench) and decided upon this version if it should add the new addon or not!
Comment 7 Lars Vogel CLA 2013-01-02 06:03:06 EST
I think we should simply offer a version for Eclipse 4.2 and another for Eclipse 4.3. as suggested in Bug 396249.

I would like to avoid the runtime check, I assume there will be other non-compliant changes in the Eclipse 4.3 platform.
Comment 8 Lars Vogel CLA 2013-03-13 06:57:01 EDT
We moved with master to Eclipse 4.3. development, hence I cherry-picked Sopots commit into master with:

http://git.eclipse.org/c/e4/org.eclipse.e4.tools.git/commit/?id=4410818c0837262bc9abfd937ad912441ae78c8c