Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

Page text matches

  • A work item was taken to understand how SML based models can be used as the integration technology to bring together the COSMOS lifecycle, from instrumentation to ...h it would like to understand in more details how SML can be used to solve integration issues.
    7 KB (1,043 words) - 13:38, 14 December 2006
  • * Don Ebright (Compuware): Cross product integration in system mgmnt with open agent infrastructure, organizing metamodels for e
    4 KB (664 words) - 13:37, 14 December 2006
  • ...ation and tool-chain concepts, provide one common mechanism of tool-chain integration, build system configuration, maintainence, etc. [https://bugs.eclipse.org/b ...another set to start execution of the target. As well any fixes to the MI integration necessary to support this environment will be done as well. [https://bugs.e
    15 KB (2,298 words) - 13:52, 22 January 2020
  • ...velopment plan for member visibility and Ian will review a plan for better integration with Eclipse.org and EPIC.
    701 bytes (112 words) - 11:27, 24 October 2006
  • #REDIRECT [[Mylyn synchronous context sharing, based on Mylyn and ECF integration]]
    83 bytes (11 words) - 18:41, 5 July 2007
  • #REDIRECT [[Mylyn synchronous context sharing, based on Mylyn and ECF integration]]
    83 bytes (11 words) - 19:38, 27 June 2007
  • == Mylyn Integration == ...ne editing for repositories such as Bugzilla, Trac, and JIRA. For the best integration with Mylyn.
    3 KB (374 words) - 14:44, 29 June 2007
  • * SML -- How do we use this as an integration technology
    5 KB (626 words) - 14:07, 14 December 2006
  • == Higgins Integration ==
    2 KB (304 words) - 14:45, 26 October 2006
  • **** Dave will start on integration work this week by Wednesday
    6 KB (841 words) - 21:14, 6 November 2006
  • ...on framework, should provide the necessary infrastructure to allow an easy integration of such services. Although the Eclipse Communication Framework (ECF) is alr
    3 KB (566 words) - 17:40, 14 October 2007
  • * [[Integration with Eclipse.org]]. Ian/Nathan/Mike T met to discuss. Ian reviewed notes ...lan for better integration between eclipse.org and EPIC. As described at [[Integration with Eclipse.org]]
    909 bytes (139 words) - 12:36, 31 October 2006
  • ...ularies in support of language translation work. SBVR is the result of the integration of these ISO standards, formal logics, linguistics, and practical experienc
    6 KB (843 words) - 10:27, 13 August 2008
  • The Core OCL component provides the following capabilities to support OCL integration:
    18 KB (2,542 words) - 11:43, 9 March 2024
  • .... EODM uses Eclipse and the Eclipse Modeling Framework (EMF) to drive this integration. It is the first design and implementation of ODM within the Eclipse, EMF a
    2 KB (326 words) - 08:44, 9 October 2008
  • ...tion Messages [http://help.eclipse.org/mars/topic/org.eclipse.ocl.doc/help/Integration.html?cp=41_1_9 (Eclipse Mars on-line help link)] This deficiency was undetected until OCL integration in UML was taken more seriously by the
    35 KB (5,422 words) - 04:04, 10 March 2021
  • <li>If you install a stable, integration build of EMF, such as No, but [http://developer.k-int.com/OpenXSD/ Knowledge Integration Ltd]. uses XSD to help support this kind of cabability and have shared thei
    41 KB (6,283 words) - 15:46, 21 May 2008
  • ...e following the format. Some projects use a format with an "I" prefix for integration builds, and an "M" prefix for maintenance builds, but this format breaks do
    9 KB (1,468 words) - 16:59, 15 November 2006
  • ...o-deployed, there likely needs to be a third party that makes sense of the integration. In your case this might be the plugin that defines the single editor. It c
    85 KB (12,481 words) - 05:16, 18 October 2011
  • Kevin McGuire gave a very nice demonstration of Websphere Integration Developer. This led to a lot of discussion on UI trade-offs. * Don't put things on the top level menu. Integration Developer used a pallete embedded in the design surface as an alternative t
    833 bytes (128 words) - 18:23, 3 November 2006

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top