EclipseSCADA/Development/RepositoryLayout

This document should describe how the repository layout of Eclipse SCADA should look like. Considering the initial contribution and the migration of the codebase of openSCADA.

New Repositories

External

All external libraries which are used but not already in Eclipse Orbit. The goal however is to migrate them sooner or later to Orbit.

Utils

Abstract: Contains tools and helper classes which are not related to SCADA functionality (UI and non-UI)

Base

Abstract: Contains tools and helper classes which are related to SCADA functionality

Contains: CA, HDS, …

Protocols

Abstract: Contains protocol implementations provided by Eclipse SCADA

Contains: mostly org.openscada.oxygen

Does not contain: Device driver implementations, these go to "Core"

Chart

Abstract: Contains the time series chart widget provided by Eclipse SCADA

Contains: Only to non-SCADA related parts of the time series widget. All chart configuration and data input modules specific to the SCADA application will got to "HMI".

This is a candidate for the Nebula Project.

Core

Abstract: The core SCADA system, all non-UI parts

Contains: Master Server Components, Device Drivers, …

HMI

Abstract: User Interface components which do not clutter up your IDE

Contains: Widgets, most of org.openscada.dakara, commands, trigger points for the common navigator framework

Does not contain: View Parts, Menu Entries

IDE

Abstract: User Interface components which may clutter up your IDE

Contains: the configurator, the OSTC and OSVI products

Releng

Abstract: Release Engineering Tool, global build and deployments scripts

Old reposotories

org.openscada.external

Will be replaced by using Eclipse Orbit.

org.openscada.jinterop

Will not be migrated to Eclipse. It will continue to exists in the openSCADA project.

org.openscada.utgard

Will not be migrated to Eclipse. It will continue to exists in the openSCADA project.