[GROOVY-1443] no AST when groovy compiler report compilation errors

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0
• Assignee: Scott Hickey
• Reporter: Louis Foucart
• Created: 01/Aug/06 07:06
• Updated: 21/Dec/09 06:49
• Resolved: 01/Aug/07 22:54

Description

When the compiler reports an error through an exception the code in GroovyProject doesn't get the AST built during the initial phases.
Here is the patch for the class GroovyProject that allows to get the AST built even if an exception occured.
I also added a catch for some hard error for which we should inform the user through a marker on the project.

private void compileGroovyFiles(final ChangeSet changeSet, final boolean generateClassFiles) {
CompilationUnit compilationUnit = createCompilationUnit("");
compilationUnit.addSources(changeSet.fileNamesToBuild());
try

{ // call the compiler compilationUnit.compile(generateClassFiles ? Phases.ALL : Phases.CANONICALIZATION); }

catch (CompilationFailedException e)

{ handleCompilationError(changeSet.getFilesToBuild(), e); }

catch(NoClassDefFoundError e)

{ GroovyPlugin.log(e); // TODO should add marker in project or similar }

// update project info that maps source files to compiled class info
CompileUnit compileUnit = compilationUnit.getAST();
updateClassNameModuleNodeMap(compileUnit.getModules());
}