我实现了一个Java插件,该插件能够使用Eclipse快速修复来修复comiper错误。要访问输入程序的最新版本,首先刷新在eclipse中打开的项目,然后调用eclipse快速修复以修复现有的编译器错误。(将对输入程序进行必要的更改,我需要首先刷新项目,然后提取最后一个版本。)实现以下代码(作为一种方法提供)以完成所描述的工作。
//Get workspace
IWorkspace workspace = ResourcesPlugin.getWorkspace();
IWorkspaceRoot root = workspace.getRoot();
//Get project
IProject project = root.getProject(projectName);
//Referesh the project
project.refreshLocal(IResource.DEPTH_INFINITE, null);
IJobManager jobManager = Job.getJobManager();
jobManager.wakeUp(ResourcesPlugin.FAMILY_AUTO_BUILD);
jobManager.join(ResourcesPlugin.FAMILY_AUTO_BUILD, null);
IJavaProject javaProject = JavaCore.create(project);
//Get ICompilationUnit (classFullName is the full name of class that we need to find its compiler error)
IType iType = javaProject.findType(classFullName);
ICompilationUnit iUnit = iType.getCompilationUnit();
/** Create working copy. It is safer to work with a copy.*/
WorkingCopyOwner owner = iUnit.getOwner();
iUnit = (owner == null ? iUnit.getWorkingCopy(null) : iUnit.getWorkingCopy(owner, null));
//Get compilation Unit
ASTParser parser = ASTParser.newParser(AST.JLS8);
parser.setKind(ASTParser.K_COMPILATION_UNIT);
parser.setSource(iCompilationUnit);
parser.setResolveBindings(true);
CompilationUnit cu = (CompilationUnit) parser.createAST(null);
//Get compiler error using eclipse quick fix
for (IProblem iProblem : cu.getProblems()) {
//If it is an error
if (iProblem.isError()) {
int offset = iProblem.getSourceStart();
int length = iProblem.getSourceEnd() + 1 - offset;
IInvocationContext context = new AssistContext(iUnit , offset, length);
ProblemLocation problem = new ProblemLocation(iProblem);
//Extract Eclipse quick fix proposal.
ArrayList<IJavaCompletionProposal> proposals = new ArrayList<IJavaCompletionProposal>();
JavaCorrectionProcessor.collectCorrections(context, new IProblemLocation[] { problem }, proposals);
}}
最后,我们在提案变量中列出了蚀提案。该程序运行良好,直到今天我遇到了一个新的编译器错误。如果我有以下示例作为输入程序:
class Test {
public void foo(){
Scanner in = new Scanner(System.in);
}
}
当我想考虑生产线提案时,出现以下运行时错误 Scanner in = new Scanner(System.in);
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ui". !STACK 1 Java Model Exception: Java Model Status [[Working copy] Test.java [in src [in SortExample]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:544)
我调试程序并找到方法问题发生collectCorrections类JavaCorrectionProcessor。
public static IStatus collectCorrections(IInvocationContext context, IProblemLocation[] locations, Collection<IJavaCompletionProposal> proposals) {
ContributedProcessorDescriptor[] processors= getCorrectionProcessors();
SafeCorrectionCollector collector= new SafeCorrectionCollector(context, proposals);
for (int i= 0; i < processors.length; i++) {
ContributedProcessorDescriptor curr= processors[i];
IProblemLocation[] handled= getHandledProblems(locations, curr);
if (handled != null) {
collector.setProblemLocations(handled);
collector.process(curr);
}
}
return collector.getStatus();
}
重要说明:对于特定类型的编译器错误,我只会收到此错误。例如,如果在未定义i的情况下此行i = 0发生编译器错误,那么我将得到unresolve变量,程序将提出解决方案,以解决任何问题。因此,我认为刷新部分应该可以正常工作,否则对于程序中所有类型的编译器错误,我都应该得到此错误。
我发现了问题。它是由于运行时错误中所示的工作副本而发生的Java Model Status [[Working copy] Test.java [in src [in SortExample]]] does not exist]
。我评论了以下几行后,一切正常。
WorkingCopyOwner owner = iUnit.getOwner();
iUnit = (owner == null ? iUnit.getWorkingCopy(null) : iUnit.getWorkingCopy(owner, null));
正如我所说,问题是由于某些特定的错误而发生的。例如,当我使用未定义整数变量(i = 0)时,不会发生这种情况,但是当在第二个类中使用一个类的实体,但是没有将其import语句添加到第二个类中时,就会发生这种情况。
发生这种情况是因为未将使用过的类添加到工作副本中,并且当eclipse想要找到使用过的类时,因为它不在工作副本中,所以它会引发异常。但是,对于第一个错误(i = 0),什么都不会发生,因为可以从工作副本中获取所有信息。
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句