Makes definitely sense, the big question is where you get the metadata
from. In the easiest case you have a bundle in your feature which
contains the metadata XML files. But such a bundle could also "manually"
create the metadata at runtime using the metadata API (we have some
cases like the Apache Felix Jetty implementation for example).
But you also might have a configuration where there is no bundle
declaring the metadata in any way in your feature; either because there
is no metadata (lazy developer) or it is declared in another feature
(ok, this might be a rare use case and we can probably ignore it)
Regards
Carsten
On 16.12.2019 15:56, David Bosschaert wrote:
Hi Robert,
That sounds like a very nice addition. I think it could be an additional
Feature Model analyser, that runs as part of the set of analysers.
I don't think it was considered before, could you please file an issue for
it?
Best regards,
David
On Mon, 16 Dec 2019 at 13:28, Robert Munteanu <[email protected]> wrote:
Hi,
Being a sloppy typist, I often get the configuration values wrong in
feature model files. I am thinking that validating the configuration
values defined in a feature model file against the metatype definition
of the matching components would help a lot.
Is there something like this planned? If not, would it make sense to
add it to the roadmap?
Thanks,
Robert
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
