Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3545

BPMN2 Eclipse Editor: automatically configure a target runtime based on eclipse project type


    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: jBPM 5.3
    • Component/s: Eclipse
    • Labels:


      See email chain:

      I think the default case is to have one runtime in one Eclipse (we have a camunda fox, jBPM 5 has jBPM 5, ...), so using that as a default is the simplest and less error prone and sufficient for most of the cases -> Perfect solution for now

      Von: Bob Brodt bbrodt@redhat.com
      Gesendet: Mittwoch, 15. Februar 2012 17:51
      An: Andreas Drobisch
      Cc: Roman Smirnov; Christian Lipphardt; Bernd Rücker
      Betreff: Re: BPMN Modeler: Runtime preselection in preferences

      Hi Andreas,

      This sounds reasonable as a fallback. I was thinking of using project facets (if installed), or possibly having the contributing plugins inspect the project artifacts to figure out what the default target runtime should be. For example, inspecting the the project's .classpath might prove useful...

      Hi Bob,

      we want to change the behavior of the BPMN2 preferences runtime selection. We want to preselect the runtime choice if there is only one plugin with runtime extension found. Both for projects and in general.

      Do you think that change would be reasonable in the core modeler?

      Best Regards,


        Gliffy Diagrams




              • Assignee:
                Rikkola Toni Rikkola
                bbrodt Robert (Bob) Brodt
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: