Hi,
Lately I was having an issue with the JessDE that could not resolve the java classes specified in a ruleset, despite the fact that they were located in the same eclipse project.
After some experimenting we discovered that the issue only occured if the eclipse project name was different from the directory it resides in.
Renaming the folder of the project and re-importing it into eclipse solved the class resolution issue, however this is unfortunately not a solution we can apply in our development environment (losing CVS history information, failing Ant builds, hysterical configuration managers...).
So it appears that the JessDE plugin assumes that the eclipse project name is always the same as the directory it's in, which is actually not an eclipse requirement.
Has anybody some ideas on how to get around this?
Ivan Op de Beeck
