Le 30/01/2020 à 17:51, Mathieu Lirzin a écrit :
Jacques Le Roux <jacques.le.r...@les7arts.com> writes:
What question have you in mind for the vote?
The idea is to vote about removing component-load.xml from the
framework, as Michael agreed on, but let them in applications and
plugins. Is that OK with your plan?
Not really but that is better than nothing.
Should the vote question include the fact that “component-load.xml”
feature will be deprecated in the next release and will be removed after
one release cycle?
Yes, that's kind of what I think about.
We are blocking this improvement because of an external use of the feature. This external use should be adapted to use the replacing mechanism. That
needs a deprecation process.
In this context, I though see 2 different things:
1. Remove component-load.xml from framework as it's not an issue for the
external use. No deprecation process needed.
2. Remove component-load.xml from applications and plugins. As it's an issue
for the external use the deprecation process is needed.
Those should be clearly separated.
Jacques
