I apologize for missing this. I did peruse the release notes, but neglected to review the JessDE docs.
Thank you. -Mitch FWIW, It appears that (require) takes a single argument. Would it make sense to allow multiple parameters as an alternative to requiring a separate (require) statements? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 9:47 AM To: [email protected] Subject: Re: JESS: Problem with 7.0a6 Hi Mitch, I think Mitch Christensen wrote: > I just installed 7.0a6 and restarted Eclipse. When I open a .clp file, > I get tons of errors due to dependency problems. These errors didn't > use to be there. The old dependency mechanism was removed and a new one implemented in this release. See http://herzberg.ca.sandia.gov/jess/docs/70/eclipse.html#dependencies: Sometimes one *.clp file depends on code in some other *.clp file having been read first; for example, rules.clp might need the definitions in templates.clp. Without these definitions, rules.clp will appear to have syntax errors. To deal with this, you can use the require* function. "require*" lets you explicitly declare these dependencies. If a file rules.clp depends on Jess commands being executed from Java, you can deal with this by creating a special file just for this purpose (you might call it ruledepends.clp That special file can contain whatever declarations are needed to make rule.clp parse properly in the editor. If you add "(require* ruledepends)" to rules.clp, then this extra file will be parsed only if it's present, as it will be during development. When you deploy the code, you can simply not deploy ruledepends.clp, and allow rules.clp to get its declarations from Java code. The "require" mechanism replaces the "Source dependencies" property sheet from earlier versions of JessDE, which is no longer supported. > Reason: > Plug-in gov.sandia.jess.editor was unable to load class > gov.sandia.jess.editor.DependencyPropertyPage." To make Eclipse forget about classes that used to be there but aren't anymore, you have to start Eclipse with the "-clean" switch after upgrading. There's a blockquote labelled "IMPORTANT!" concerning this in the manual now. > Hi, > > Explorer and selected Properties to display the properties page. I then > clicked on Source Dependencies and got the following error dialog box: > > "Unable to create selected property page. > > > with an [OK] button. > > This happens all the time, for all source (.clp) files. > > I did install all four plugins (from a6). > > I'm going to continue analyzing the situation here, but thought I'd post > in case I've done something obvious/stupid. > > -Mitch --------------------------------------------------------- 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://herzberg.ca.sandia.gov -------------------------------------------------------------------- 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] -------------------------------------------------------------------- -------------------------------------------------------------------- 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] --------------------------------------------------------------------
