We have to distinguish between the json representation of a feature as
defined in our "specification" and the additional support of our maven
plugin.
A feature must have an ID and we don't allow interpolation of
placeholders within the feature. Therefore the json code that we have to
read a
Hi Simo,
Take this with several grains of salt as I don't know the internals of the
feature processing, but just looking at your email from a generic "how do I
process a JSON file" it still seems inefficient.
Ideally, IMO, the substitution would be done as a filter applied to the
stream of parser
Hi all mates,
during the last couple of months the work we've been doing on Feature
files processing is HUGE, so the iterations to refine the pipeline
process introduced some "overhead" operations we can improve, what we
currently do is:
* the pre processor starts by reading the whole file to
