Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Addons execution order changed in Eclipse 4.4
Addons execution order changed in Eclipse 4.4 [message #1397247] Wed, 09 July 2014 12:43 Go to next message
Pierre GAUTIER is currently offline Pierre GAUTIERFriend
Messages: 13
Registered: August 2010
Junior Member
Hello,


I'm working on a pure e4 application, that basically only contains an Application.e4xmi and defines a LifeCycleHandler with corresponding life cycle annotations.

I need the product highly modular therefore I rely on the E4 extension parsing to load modules.

Each module starts, registers and do things through its x.y.z.ModuleNameAddon defined within a fragment.e4xmi, eventually with other model things (perspectives, parts, etc.).

With Eclipse 4.3, addons were executed respecting the order of required plugins : if a plugin A required a plugin B, the BAddon was executed before AAddon.

In Eclipse 4.4 it seems this order isn't respected anymore which causes me many problems. Was it done on purpose or is it a regression ?

The problem may have been introduced when refactoring ModelAssembler.topoSort() to ExtensionsSort().sort()


I remain at your disposal for any further information.


Regards,

Pierre GAUTIER
Re: Addons execution order changed in Eclipse 4.4 [message #1397250 is a reply to message #1397247] Wed, 09 July 2014 12:48 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6599
Registered: July 2009
Senior Member
this is a regression see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=438736

Tom

On 09.07.14 14:43, Pierre GAUTIER wrote:
> Hello,
>
>
> I'm working on a pure e4 application, that basically only contains an
> Application.e4xmi and defines a LifeCycleHandler with corresponding life
> cycle annotations.
>
> I need the product highly modular therefore I rely on the E4 extension
> parsing to load modules.
>
> Each module starts, registers and do things through its
> x.y.z.ModuleNameAddon defined within a fragment.e4xmi, eventually with
> other model things (perspectives, parts, etc.).
>
> With Eclipse 4.3, addons were executed respecting the order of required
> plugins : if a plugin A required a plugin B, the BAddon was executed
> before AAddon.
>
> In Eclipse 4.4 it seems this order isn't respected anymore which causes
> me many problems. Was it done on purpose or is it a regression ?
>
> The problem may have been introduced when refactoring
> ModelAssembler.topoSort() to ExtensionsSort().sort()
>
>
> I remain at your disposal for any further information.
>
>
> Regards,
>
> Pierre GAUTIER
Re: Addons execution order changed in Eclipse 4.4 [message #1397255 is a reply to message #1397250] Wed, 09 July 2014 12:57 Go to previous messageGo to next message
Pierre GAUTIER is currently offline Pierre GAUTIERFriend
Messages: 13
Registered: August 2010
Junior Member

Oh well, thanks for your quick answer.
Re: Addons execution order changed in Eclipse 4.4 [message #1397271 is a reply to message #1397255] Wed, 09 July 2014 13:29 Go to previous message
Brian de Alwis is currently offline Brian de AlwisFriend
Messages: 877
Registered: January 2012
Senior Member

Sorry Pierre.

I thought we had code that would loop through fragments with still-unresolved imports until it reached a fixpoint, such that this topological sort was intended to be an optimization.

Brian.
Previous Topic:Setting Custom Context Variables In A Part's Context Before Part Creation
Next Topic:Updating command contributions on handler switch
Goto Forum:
  


Current Time: Tue Jun 15 08:10:54 GMT 2021

Powered by FUDForum. Page generated in 0.01885 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top