Yes, adding OpenIDE-Module-Module-Dependencies by hand is pretty old school
:-)
--emi
sâm., 15 aug. 2020, 14:37 Patrik Karlström a scris:
> This is really cool,
> first I noticed that the nbm-maven-plugin supports
> configuration,
> then that I don't have to use them. :)
>
> Looking at a modul
This is really cool,
first I noticed that the nbm-maven-plugin supports
configuration,
then that I don't have to use them. :)
Looking at a module's *generated* manifest tells me that they end up there
due to their maven dependency. Nice!
Den fre 14 aug. 2020 kl 18:42 skrev Patrik Karlström :
>
What we need is a debug flag that loads the modules at random if possible
(while still respecting the topological sort as defined by dependencies).
This would show all kind of assumptions you didn't thing about.
--emi
vin., 14 aug. 2020, 19:43 Patrik Karlström a scris:
> Hi,
>
> Den fre 14 aug.
Hi,
Den fre 14 aug. 2020 kl 11:39 skrev Emilian Bold :
> I feel you are enumerating a whole bunch of workarounds you already
> thought about without giving us an example of the real issue you
> experienced.
>
I was unable to, and still am, specifying the issues, but one of the
symptoms was that
I feel you are enumerating a whole bunch of workarounds you already thought
about without giving us an example of the real issue you experienced.
Normally, modules can be installed and enabled and disabled by users are
any time.
If your app is somehow erratic now it means there's a hidden depende
Lately I've been experiencing problematic behavior in a platform
application with close to 40 modules, NetBeans ones un-counted.
I believe that it's related to the fact that I did not declare
any OpenIDE-Module-Module-Dependencies in the manifests and that the module
load order changed somehow.
I
