Skip to main content
Jump to: navigation, search

Difference between revisions of "STEM Releng"

(New page: == STEM Release Engineering == This page details how to operate the STEM builder to create binary, platform-specific builds of STEM. ''' This information is for advanced users and committ...)
 
(Adding a new plug-in to an existing feature)
Line 16: Line 16:
  
 
=== Adding a new plug-in to an existing feature ===
 
=== Adding a new plug-in to an existing feature ===
 +
STEM is built from Eclipse plug-ins.  This section describes how to add one or more new plug-ins to the STEM build process to an ''existing'' feature.  If you want to create a new feature, see the next section.
  
 
+
# Determine which Feature(s) the plug-in(s) should be added to
 +
#: '' See note above about feature cross-dependencies to help determine which features you should add the plug-in to ''
 +
# In Eclipse, expand the feature project the plug-in(s) should be added to and double-click ''' feature.xml '''
 +
# In the '''Feature Editor''', select the '''Plug-ins''' tab
 +
# On the '''Plug-ins and Fragments''' page, click the '''Add...''' button
 +
# In the '''Plug-in Selection''' dialog, type the name of the plug-in you wish to add.  When it shows up in the list, select it and click ''' OK '''
 +
#: '' Repeat this step for all plug-ins you wish to add to this feature ''
 +
# Save '''feature.xml''' (''File-Save or Control-S'')
 +
# Add the plug-in to SVN by right-clicking on the project, highlighting ''' Team ''' and selecting ''' Share Project'''.  Follow the steps to add it to the repository.
 +
#: ''' Note: ''' The STEM Source Repository has a specific layout.  Please make sure to place your new plug-in an appropriate location.  Often the plug-ins are grouped in folders with plug-ins of similar functionality (such as '' disease models '')
  
 
=== Adding a new feature ===
 
=== Adding a new feature ===

Revision as of 13:08, 29 July 2011

STEM Release Engineering

This page details how to operate the STEM builder to create binary, platform-specific builds of STEM. This information is for advanced users and committers only.

Background

The STEM build process is built on several foundational pieces of the Eclipse Platform. These pieces include:

  • Eclipse Products
  • Eclipse Features
  • PDE Build Process
  • P2 Provisioning

These fundamental aspects of the Eclipse Platform are orchestrated to build platform-specific binaries of STEM.

Adding New Code to the Builder

This section describes how to add new plug-ins, features, and third-party dependencies to the STEM Build process.

Adding a new plug-in to an existing feature

STEM is built from Eclipse plug-ins. This section describes how to add one or more new plug-ins to the STEM build process to an existing feature. If you want to create a new feature, see the next section.

  1. Determine which Feature(s) the plug-in(s) should be added to
    See note above about feature cross-dependencies to help determine which features you should add the plug-in to
  2. In Eclipse, expand the feature project the plug-in(s) should be added to and double-click feature.xml
  3. In the Feature Editor, select the Plug-ins tab
  4. On the Plug-ins and Fragments page, click the Add... button
  5. In the Plug-in Selection dialog, type the name of the plug-in you wish to add. When it shows up in the list, select it and click OK
    Repeat this step for all plug-ins you wish to add to this feature
  6. Save feature.xml (File-Save or Control-S)
  7. Add the plug-in to SVN by right-clicking on the project, highlighting Team and selecting Share Project. Follow the steps to add it to the repository.
    Note: The STEM Source Repository has a specific layout. Please make sure to place your new plug-in an appropriate location. Often the plug-ins are grouped in folders with plug-ins of similar functionality (such as disease models )

Adding a new feature

Adding a new third-party dependency

Running the STEM Builder

Setting up your environment

Checking out the source from SVN

Running the STEM Builder

Running the JUnit Tests

Continuous Integration (CI) Automated Builds

Back to the top