On Dec 1, 2006, at 5:36 AM, Bergner, Olaf (Saxonia) wrote:
With Jess 7.0 out the doors, we are starting to use its set of
Eclipse plugins. However, the Jess editor complains about not being
able to resolve _any_ imported java class. I suspect that this is
related to
http://www.mail-archive.com/[email protected]/msg08255.html
which, unfortunately, was left unanswered. So I would like to
repeat the question: is there a workaround for the case when a
project's name is not identical to the name of the project folder?
This is a known problem.
The current version of the JessDE uses your actual compiled class
files. If Eclipse is set up so that the compiled class files end up
outside the workspace (as is the case if you import a build.xml to
create a project, for example) then for reasons that are not clear to
me, these locations aren't included in the project classpath that's
available to plugins like the JessDE. Even if you include these
directories explicitly in the "Project Build Path", Eclipse does not
pass them to the JessDE at the crucial moment; they seem to be
deliberately removed.
There are two possible fixes: one is for the JessDE to use Eclipse's
classfile parser; this is a good goal and the right solution, but
difficult to implement. The other would be for the JessDE to somehow
find out about these additional directories by itself; it's not clear
how to do this either.
In either case, expect a fix in a future point release.
---------------------------------------------------------
Ernest Friedman-Hill
Advanced Software Research Phone: (925) 294-2154
Sandia National Labs FAX: (925) 294-2234
PO Box 969, MS 9012 [EMAIL PROTECTED]
Livermore, CA 94550 http://www.jessrules.com
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
