-------------------------------------------------------------------- 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] --------------------------------------------------------------------
Wrestled for number of hours with issue I solved months ago and
forgot, and thought this might be useful for others. If you are
using Jess in an Eclipse application, recall the buddy registration
system solves classpaths, etc. Thus, the plugin manifest now has a
registration statement in it. However, be certain that your own
application manifest has the specific plugin listed as one to whom it
will publish. I made a ridiculous error. In past version I created
a jess.core plugin that wrapped the older version, and in my
application, I indicated that jess.core should be a buddy. But this
time, I added gov.sandia.jess as a dependency instead; when this
failed, I created a plugin called jess7.core, to distinguish from the
older one. But I forgot to fix the manifest.mf file of my actual
application, which still referred to jess.core. Fixing this
completely eliminated the path errors I mentioned earlier.
- JESS: Announcing Jess 7.0RC3 Ernest Friedman-Hill
- Re: JESS: Announcing Jess 7.0RC3 J Michael Dean
- Re: JESS: Announcing Jess 7.0RC3 Ernest Friedman-Hill
- Re: JESS: Announcing Jess 7.0RC3 J Michael Dean
- JESS: Adapting Eclipse J Michael Dean
- JESS: Using Jess in Eclipse RCP J Michael Dean
- Re: JESS: Announcing Jess 7.0RC3 J Michael Dean
