Thanks Thomas!
A thorough answer. The text gives a very good explanation and is well written.
Put it in the manual!
The conclusion is then to make as few dependencies as (as we always should)
possible in any reusable class as the class ids "always" become dependent after
generation. No except
On 10/04/2011 11:59 AM, Stefan Andersson wrote:
Can you tell us more about how the generator dependency analysis of
links between classes are done in practice.
The generator starts with the classes given in the "include"
configuration key of the job. For each class, it parses the class code
Can you tell us more about how the generator dependency analysis of links
between classes are done in practice.
How does a dependency look like to include a class at generation?
Does it include ALL dependencies even though a dependency never might be
reached at runtime due to custom code usage?
