Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

  • ...It provides samples of Buckminster code as XML fragments, and illustrates common usage scenarios. ...available locally in a repository cache, they would be fetched from some common designated master site for all teams.
    67 KB (9,899 words) - 20:05, 14 February 2009
  • * <code>org.eclipse.cosmos.me.dmtoolkit.common</code> - contains code common to both J2EE and OSGi deployment scenarios <li> org.eclipse.cosmos.common
    22 KB (3,208 words) - 19:53, 18 February 2008
  • ...and that is exemplified in top-level tooling platforms that, like Eclipse STP or the recent SCOrWare proposal made by several Objectweb members (includin ...ight, one of the natural goals of JWT is good integration with the Eclipse STP platform.
    23 KB (3,434 words) - 13:50, 22 January 2007
  • ...pate in Orbit project to move our commonly needed third-party content to a common Eclipse repository. :begin by creating a common site at Apache for components such as Axis2, Woden, Tomcat, Geronimo
    19 KB (2,811 words) - 16:36, 8 May 2007
  • ...nt for a discussion on the internal representation of artefacts in Eclipse STP. ...d be created for making the conversion between the meta-model of A and the meta-model of B.
    8 KB (1,380 words) - 13:24, 20 February 2008
  • ...plug-in within the Eclipse IDE. Although Buckminster can be used to solve common build, assemble & deploy problems, it is ''not'' a build or component manag ...th an optional MSPEC, workspaces can be materialized in no time ensuring a common ground.
    13 KB (1,925 words) - 09:30, 22 June 2007
  • ...plug-in within the Eclipse IDE. Although Buckminster can be used to solve common build, assemble & deploy problems, it is ''not'' a build or component manag ...th an optional MSPEC, workspaces can be materialized in no time ensuring a common ground.
    13 KB (1,925 words) - 20:39, 14 February 2009
  • ...al Model Discussion|here]]. A [[sample scenario involving the intermediate meta-model|simplified sample scenario]] involving the IM is also available. ...ptual reasoning platform for SOA, its purpose is rather to capture as much common SOA design information from different editors as possible. In particular it
    10 KB (1,443 words) - 22:29, 10 May 2008
  • ...clipse. Its large audience, counting significant Eclipse adopters project (STP, TPTP, GMF, ...) as well as major companies products (Rational® Software A * To define an Ecore meta-model based UI integration framework
    7 KB (946 words) - 12:33, 19 December 2010
  • ...e Provider should provide source code for corresponding class. b)Integrate common JDT search possibilities (for example "Search\References") with Google Code | [[STP/BPMN_Component|BPMN]]
    46 KB (7,079 words) - 00:24, 6 November 2008
  • * Common build infrastructure for smaller projects. Configuration will be done via p ...4.0=HEAD,/opt/public/stp/apps/IBMJava2-ppc-142 -or- 3.4.0=HEAD,/opt/public/common/ibm-java2-ppc-50 -- defines version, CVS branch, and path to java
    4 KB (711 words) - 14:13, 3 July 2008
  • ...EMF is widely used by Eclipse projects, e.g., UML2, WTP, TPTP, DTP, GMF, STP, but also as the de facto reference implementation of the Object Management ...ld accomplish. Attendees will be encouraged to discuss potential areas of common interest and how a collaboration could work.
    12 KB (1,718 words) - 16:48, 11 December 2008
  • ...Those classes must be available to JWT and specified in the workflow file. STP-IM -like properties are in this case. Christian Saad's proposition for the ...asic idea is that dynamic properties are specified using a small, external meta-model, in which a set of properties is part of a special container element (just
    12 KB (1,801 words) - 15:48, 5 January 2009
  • ...jor part on the [[STP/SCA_Component/SCA_Composite_Meta_Model|SCA Composite meta-model]]. It is then completed by additional parts, but there are few of them. * That composites are valid XML files (covered indirectly by the meta-model).
    8 KB (1,394 words) - 10:56, 8 July 2010
  • *SCA Common: SCA nature, wizard for the creation of new SCA assembly files, preference [[Category:STP]]
    4 KB (569 words) - 04:49, 9 November 2010
  • | '''STP:''' * (''old'') '''Tom S''' Athena Common Builder Cookbook
    11 KB (1,700 words) - 17:01, 20 March 2011
  • *Constraint Definition - Provides API for defining constraints for any EMF meta-model (batch and live constraints). ** Common EPP feature included in all packages
    45 KB (6,657 words) - 13:53, 17 June 2010
  • 1. (the most common) As a developer, you'll want to debug your code and the JWT code you build * '''jwt-transformation-stpim''' ''Bridge with SOA Tool Platform (STP)'s Intermediate Model''
    13 KB (1,834 words) - 09:57, 1 July 2015
  • ...to use a heavy-weight application should if they didn't need to. The most common example of this is to ship the Dashboard plugin independently, allowing non may chose any of them to use; in this tutorial we will open top.stp. Go ahead and open the file.
    79 KB (13,224 words) - 08:46, 12 March 2012

Back to the top