Good point. I agree. I added a jira issue: http://www.fornax-platform.org/tracker/browse/CSC-281 /Patrik
Heiner.M wrote: > > Hello, > > in my sample the code generated by Sculptor has java compile errors due to > missing import statements. > > If I understand JavaImportBeautifier correctly, only for those classes > imports are generated which occur with full qualified class name in the > java source. > > As reason I believe Sculptor generates partly Non-Full-Qualified class > names, which works only in cases when the same class name is generated > with full-qualified name at another occurance in the same file --- which > is not always the case. > > When I switch of the import statement generation: > <beautifier class="org.hybridlabs.source.formatter.JavaImportBeautifier" > organizeImports="false" format="true"/> > I get many more compile errors ! > > Shouldn't the Sculptor templates use always full-qualified class names > (only before use of JavaImportBeautifier), in order that the code compiles > even without generated import statements ? > > Maybe, for quality checking, the Sculptor templates should always tested > without import statement generation ? > > Heiner > -- View this message in context: http://www.nabble.com/Missing-java-imports-in-sculptor-generated-code-tp21578816s17564p21581596.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
