| Addons execution order changed in Eclipse 4.4 [message #1397247] |
Wed, 09 July 2014 08:43  |
Eclipse User |
|
|
|
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 08:48  |
| Eclipse User |
|
|
|
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
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03958 seconds
Home