News entries for March 2014

2014-03-26 Milestone release M5

Nearing the 0.1.0 end of April we pushed out another milestone build (M5) which irons out some issues we had with the previous release.

The focus was on bugfixing and cleaning up stuff as resources and meta data. The plan is to freeze the current state and use it for the final 0.1.0 build. Unless we find some serious issue of course.

So now it is time for us and the Eclipse Staff to do our legal work in order to get out the release.

Nearing the 0.1.0 end of April we pushed out another milestone build (M5) which irons out some issues we had with the previous release.
Full article
2014-03-14 Milestone release M4

On the road to our first 0.1.0 release we did create milestone release 0.1.0-M4.

The most notable additions are the MSI based deployment in the configurator application and the ability to directly use Eclipse SCADA artifacts as a Maven 2 repository, in addition to the already existing P2 repository.

The configurator application can now create deployments for the Windows platform using MSI. Since MSI is all different than RPM or DEB, it is a totally different workflow. Also not all features of the Linux based deployment are available. But it is a good start. All this is based on the WiX Toolset. The configurator created ready to run Ant and WiX build files which can then be processed either locally from the Eclipse IDE or on a separate build server.

In addition to providing P2 repositories, also a plain maven 2 repository is being created. Also see EclipseSCADA/GettingStarted/WithMaven in the wiki. It is a conversion of the P2 artifacts and metadata, but honors some parts of maven 2 repositories. The idea was to easily add Eclipse SCADA to an already existing maven 2 based project. Together with fortiss GmbH we added Eclipse SCADA to their Akka based simulation framework.

In addition to our original schedule we will add an additional (M5) milestone before we perform the final release in the end of April.

On the road to our first 0.1.0 release we did create milestone release 0.1.0-M4. The most notable additions are the MSI based deployment in the configurator application and the ability to directly use Eclipse SCADA artifacts as a Maven 2 repository, in addition to the already existing P2 repository.
Full article
2014-03-12 Creating maven repositories

Eclipse SCADA is built using Tycho. While tycho is based on maven, is does not produce a usable maven repository output if you are using the "manifest first" approach.

In the recent nightly build we started to convert the P2 repository to a maven 2 compatible layout. The output will also be available for the upcoming M4 milestone build.

For more information about the conversion and how to use the repositories see https://wiki.eclipse.org/EclipseSCADA/GettingStarted/WithMaven.

Eclipse SCADA is built using Tycho. While tycho is based on maven, is does not produce a usable maven repository output if you are using the "manifest first" approach. In the recent nightly build we started to convert the P2 repository to a maven 2 compatible layout. The output will also be available for the upcoming M4 milestone build.
Full article
2014-03-06 Common driver MSI package

In order to better support server deployments on the Windows system (bug #428905), we started to provide ready to run common driver packages.

The package is available for 32bit and 64bit Windows installations and actually provide two things. First they install a ready to run common driver setup. Although it is disabled for automatic startup in the service control manager, it can be activated through the windows service layer pretty easily.

Second, it creates a base which can be used for the new MSI deployment system in the configurator application. Since everything works different on Windows, also the workflow is a bit different here. The configurator application allows to create specific deployment packages for each node in the system. But in the case of MSI, these also contain the binaries. This makes the packages a bit bigger and reduced the flexibility a bit, but on the other hand provides a much cleaner setup experience.

The main entry point for more information is the wiki page, which describes not only the common driver installation, but all MSI packages.

In order to better support server deployments on the Windows system (bug #428905), we started to provide "ready to run" common driver packages.
Full article