Issue 142 in soar: SoarEditor dies on init with certain files/folders in eclipse project

[so...@googlecode.com]

Status: Accepted
Owner: maz...@gmail.com
Labels: Type-Defect Priority-Medium

New issue 142 by maz...@gmail.com: SoarEditor dies on init with certain
files/folders in eclipse project
http://code.google.com/p/soar/issues/detail?id=142

What steps will reproduce the problem?
Hard to reproduce. Some file or folder structure I accidentally had in a
project with my agents caused the SoarEditor to stop working. Telling
eclipse to exclude all non-soar resources (a single folder in my case) from
the project resource list or manually deleting/moving the files allowed the
SoarEditor to work again. When I have more time, I'll try to figure what
about that folder caused the issue.

What is the expected output? What do you see instead?
SoarEditor will not open or display any .soar file. Instead you will get
the error "Problems occurred when invoking code from
plug-in: "org.eclipse.jface"." and an empty tab will open with no title or
content. Just an X.

Note that datamap editor and other SoarEditor functionality will still work.

Please use labels and text to provide additional information.

Occurs in this part of SoarEditor.java. Some file is causing it to die on
the line "if (member instanceof IFile &&
member.getFileExtension().equalsIgnoreCase("dm"))":

private static ArrayList<IFile> findDatamaps(IResource input)
{
ArrayList<IFile> ret = new ArrayList<IFile>();
IContainer parent = input.getParent();
if (parent == null) return ret;
try
{
for (IResource member : parent.members())
{
if (member instanceof IFile &&
member.getFileExtension().equalsIgnoreCase("dm"))
{
ret.add((IFile) member);
}
}
}

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[so...@googlecode.com]

Comment #1 on issue 142 by maz...@gmail.com: SoarEditor dies on init with

certain files/folders in eclipse project
http://code.google.com/p/soar/issues/detail?id=142

The soarerror file that is created when soar has a fatal error will cause
this problem.