jUCMNav v3.1.0

Download

Update site (recommended)

  • NEW See InstallationDemo
  • NEW Dependencies on GEF, EMF, OCL, and others now handled automatically through the update site.
  • In Eclipse: Help -> Software Updates -> Find and Install -> Search for new features to install -> New remote site:
  • Select both the new jUCMNav update site and the Europa Discovery Site
  • Important Notes
    • You might need to expand the Europa Discovery Site before clicking on "Select Required" (dependencies).
    • Using the update site is needed if you want the MSC Viewer plugin to be installed properly. Afterwards, the jUCMNav and MSC Viewer plugins can be updated manually from binaries.
    • Eclipse does not allow automatic upgrades between major revisions. jUCMNav v2.* will need to be uninstalled before proceeding with the installation of jUCMNav v3.*

  • Download v3.1.0 here (jar).
    • Make sure your browser doesn't rename the .jar file to .zip or anything else.
  • Other files (src, javadoc)
  • Download and install all prerequisites, then copy the jar file into your /eclipse/plugins/ directory. Restart Eclipse.
  • If you've installed jUCMNav from a latest build instead of an official release, make sure you remove the latest builds.

Requirements

Operating Systems

  • Windows XP (tested) :check:
  • Linux (tested) :check:
  • MacOS X (tested) :check:
  • Any other O/S on which you can run Eclipse (currently untested - please report your success!)

JDK

  • J2SE 5.0 (1.5)
  • Note: J2SE 6.x may cause issues with the installation and execution of jUCMNav.

Eclipse

  • Version
    • jUCMNav 3.1 requires Eclipse 3.3
  • Distributions
  • Plug-ins required for running jUCMNav
    • jUCMNav 3.1 requires the Eclipse EMF, GEF, JDT, RPC, OCL, and Platform plugins.
    • Users should use the jUCMNav update site to get these dependencies automatically.
    • Otherwise, they can be obtained from the Europa Update Site or from their respective projects
  • [Optional] Additional plug-ins required for compiling jUCMNav

GraphViz

Release Notes

Installation

  • For more in-depth information and a guide about installation of prerequisites, see DevDocDeployment.
  • For complete notes and troubleshooting, see: JUCMNavDeployment

Help

  • End-user documentation is integrated with the Eclipse help system. Access Help > Help Contents from the Eclipse workbench, then select topic jUCMNav Online Help.
  • The latest user documentation can also be accessed via HelpOnLine

Reporting Bugs / Usability Requests

  • Send your bug reports to jucmnav-dev@softwareengineering.ca.
  • Include reproduction steps, sample .jucm files and, if applicable, copy-paste the error log messages.
  • If you're zealous enough, we'll create a BugZilla account for you smile

Enhancements / Fixes since 3.0.0

Bug Description
550 Error when undoing the deletion of a GRL element
554 Strategies export to .csv files do not handle commas in descriptions
556 In the Stub Bindings window, plug-in condition expressions' && are replaced with &
555 Belief descriptions not duplicated properly when duplicating a GRL diagram
551 Report when transforming a non-well-nested UCM
552 TOC links in the on-line help refer to the TWiki site
535 And/Or decomposition context menu item
559 Invalid thread access when exporting a URN model without scenario definitions
561 Invalid default value for Preferences under Linux
409 Export wizard + multi-map select
332 Image export: should try to trim exported images
329 Progress meters for wizards

Known Issues in 3.1.0

  • Reports generated, MSC Viewer, and user documentation only available in English.
  • Reports do not include information on GRL elements or UCM scenario definitions (and MSCs)
  • Visibility of GRL contribution icons and text now can be set via jUCMNav's main preference page, but open editors are not automatically updated. You need to reload the model.
  • Deleting a map whose start point is referenced in a scenario definition causes saving the file to complain.
  • There are no extension points to give your own scenario/strategy algorithms and no UI to choose them.
  • Memory leak. With very large diagrams (30+ complex maps), you might only be able to open it half a dozen times before you run out of memory. Restart Eclipse to clean memory or increase JVM heap space until we find the memory leak source.

-- DanielAmyot - 02 May 2008
Topic revision: r2 - 02 May 2008, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback