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

Difference between revisions of "EclipseSCADA/Release/0.1.0"

 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Note||This page gathers all information about the *upcoming* release 0.1.0.}}
+
== More Information ==
 +
 
 +
* Download page for 0.1.0 : http://www.eclipse.org/eclipsescada/releases/0.1.0/
 +
* Presentation on Slide Share : http://www.slideshare.net/dentrassi1/eclipse-scada-release-010-34133871
  
 
== New and noteworthy ==
 
== New and noteworthy ==
  
* Rename all and everything from "openSCADA" to "Eclipse SCADA" … in various variants
+
* Migrate from openSCADA to Eclipse SCADA
 +
** Rename all packages and system properties to "org.eclipse.scada"
 +
** Rename XML namespaces to "http://eclipse.org/SCADA"
 +
** Change all labels from "openSCADA" to "Eclipse SCADA"
 +
** See also [[EclipseSCADA/MigrationFromOpenSCADA]]
 
* Add modbus exporter functionality – https://git.eclipse.org/r/#/c/18401/
 
* Add modbus exporter functionality – https://git.eclipse.org/r/#/c/18401/
 
* A REST exporter that allows access to DA items, reading and writing
 
* A REST exporter that allows access to DA items, reading and writing
Line 11: Line 18:
 
** Server launchers to test the output locally
 
** Server launchers to test the output locally
 
* Added some debug and analysis tools
 
* Added some debug and analysis tools
 +
* Change the build system to Maven Tycho
 +
** Provide RPM, DEB and MSI files
 +
** Sign packages and MSI files
 +
** Provide Maven 2 repositories
 +
 +
{{Note|Java 8|Some components of Eclipse SCADA 0.1.x are not compatible with Java 8. Mostly due to changes in the JavaScript engine Nashorn. It is recommended to use Java 7 for Eclipse SCADA 0.1.x. Eclipse SCADA 0.2 will bring support for Java 8}}
 +
 +
== Maintenance releases ==
 +
 +
The following section lists the maintenance releases for 0.1.0. Each section contains the changes to its predecessor.
 +
 +
=== 0.1.2 ===
 +
 +
* Fix configuration parsing issue with the dave driver
 +
* Add VI editors to their feature so they get installed by the marketplace
 +
 +
=== 0.1.1 ===
 +
 +
* Fix some issues with deployments in Suse Linux
  
 
== Changes during the release cycle ==
 
== Changes during the release cycle ==

Latest revision as of 05:14, 17 June 2014

More Information

New and noteworthy

  • Migrate from openSCADA to Eclipse SCADA
  • Add modbus exporter functionality – https://git.eclipse.org/r/#/c/18401/
  • A REST exporter that allows access to DA items, reading and writing
  • An IDE based configuration system
    • With a structured editor for the Eclipse IDE
    • Deployments for Redhat (rpm), Debian/Ubuntu (deb) and Windows (MSI)
    • Server launchers to test the output locally
  • Added some debug and analysis tools
  • Change the build system to Maven Tycho
    • Provide RPM, DEB and MSI files
    • Sign packages and MSI files
    • Provide Maven 2 repositories
Note.png
Java 8
Some components of Eclipse SCADA 0.1.x are not compatible with Java 8. Mostly due to changes in the JavaScript engine Nashorn. It is recommended to use Java 7 for Eclipse SCADA 0.1.x. Eclipse SCADA 0.2 will bring support for Java 8


Maintenance releases

The following section lists the maintenance releases for 0.1.0. Each section contains the changes to its predecessor.

0.1.2

  • Fix configuration parsing issue with the dave driver
  • Add VI editors to their feature so they get installed by the marketplace

0.1.1

  • Fix some issues with deployments in Suse Linux

Changes during the release cycle

Changes since RC1

  • Bug fixes
    • Fix script engine bug 433409 for Java 8 and other non-hotspot/non-openjdk based VMs
    • Fix RPM dependencies for Suse

Changes since M4

  • Bug fixes
    • Fix some dependency issues with the .deb files
    • Fix the startLevel.properties file/uri mixup
    • Add a way to reduce the path length during the MSI deployment on windows to reduce the file name. Windows/MSI has problems with file names longer than 250 characters

Changes since M3

  • Bug fixes
    • Fixed a connection edit bug that causes the service id to be deleted
  • Modifications
    • Changed backend of preferences/registry based connection store to use single nodes. Old entries are not migrated at the moment.
  • Additions

Changes since M2

  • Bug fixes
  • Modifications
    • Refactored several models in IDE
  • Additions
    • Added the HD spy
    • Added DA item console

Changes since M1

Back to the top