Support
JIVE is an interactive execution environment developed by the Department of Computer Science and Engineering at the University at Buffalo. JIVE was originally designed as a stand-alone Java application. Recently, it was redesigned for the Eclipse Platform. JIVE is released under the Eclipse Public License (EPL) agreement.
Contacts
The following people are responsible for JIVE's development and maintenance. Questions or concerns can be addressed to the appropriate individual.
- Demian Lessa - Eclipse Plug-in Developer and Researcher (active)
- Jeffrey K. Czyz - Eclipse Plug-in Developer and Researcher (inactive)
- Dr. Paul V. Gestwicki - Stand-alone JIVE Developer and Researcher (inactive)
- Dr. Bharat Jayaraman - Faculty Adviser and Researcher (active)
Development Roadmap
JIVE is currently under active development. New features and improvements will be announced in the News section as they become available. Those willing to contribute to JIVE should contact the developers for more information. As of September 2010, our focus is on the following features:
- Incorporation of a scalable temporal data model and query engine for JIVE, to support high-level declarative temporal queries.
- Notational extensions to the diagrams in order to represent missing information caused by event trace filtering.
- Scalability extensions to the diagrams in order to reduce the amount of information presented, without compromising the meaning of the diagram as a whole.
- Layout improvements to the diagrams.
- Refactoring of the event tracing subsystem.
API Documentation
Most of the API documentation for JIVE is available online in Javadoc form. More documentation will be added during future releases.
Changelog
Changes from release-to-release are cataloged and can be viewed in the changelog.
Issue Tracking
An issue tracking system will be put in place in the near future. In the mean time, any problems can be directed to the Eclipse Plug-in developer listed above.
Known Issues
- Exceptions caught in filtered classes can cause incorrect sequence model behavior.
- Superclass method contours appear next to their context's derived-most contour when contours are stacked.
- Instance contours are not created for arrays.
- Assignments to array cells are not monitored.
- Individual contours cannot be expanded or collapsed.
- Programs generating a large number events can exhaust the heap.
- Lifeline heads on the sequence diagram do not scroll.


