Use ImportUtil to manage imports in templates about spray HOT 6 CLOSED

The class XtendProperties in Spray also contains an import manager that is used 
already in some of the Spray templates.  I just did no get around to use it in 
all templates. Can we compare the use of ImportUtil and XtendProperties ?

I will investigate the use of XtendProperties. The import manager used there is 
quite simple. I have leveraged the one from EMF, which is far more advanced. I 
am not completely sure in which extend it does also more for us. But I'd prefer 
to reuse such a component before having an own one.

Sounds like a good idea, if the already existing one ash everything we need, 
let's reuse it.

I have documented the pattern here:
http://code.google.com/a/eclipselabs.org/p/spray/wiki/DevGuide_Generator?ts=1317
117450&updated=DevGuide_Generator#Import_Organizing

If possible I want to get rid of calling 'importUtil.initImports', or just move 
it to FileGenerator.

Moved logic to FileGenerator and refactored template code. Using the 
"MARKER_IMPORT" marker comment.

Updated DevGuide: 
http://code.google.com/a/eclipselabs.org/p/spray/wiki/DevGuide_Generator