...
| No more ".git" extension for checked out projects | Since git automatically removes the ".git" extension we changed our build scripts to respect that. It sure was easy to identify a git repository in the workspace by the ".git" extension. But we go with the default now. |
|---|---|
| Provide Target Platform Files | Starting with openSCADA 1.1 we will provide target platform files which make it a lot easier to set up an Eclipse workspace for openSCADA. |
| Update external components | openSCADA 1.1 uses:
Also we will remove/replace unused libraries. We will try to only use external bundles from the Eclipse Orbit repository. |
| Remove non-core bundles | There are some bundles which were needed in some customer projects, which might be useful for some other users, but are not really a core part of openSCADA (for instance all the spring integration bundles). They will not disappear, but will be moved to a contrib feature/repository. |
| Clean up dependencies | Spring and its dependencies have all been moved to the contrib repository in order to clean up a mess of external dependencies. Also the osgi.externprise enterprise bundle is imported now from Eclipse Gemini (http://www.eclipse.org/gemini/dbaccess/) instead of the one from openSCADA. |
| Tycho Build / Maven | We added the necessary configuration (POM Files) for the Tycho Build to build the projects: aurora, utgard, oxygen and atlantis. Others will follow in the future. So now it is possible to build an openSCADA based application using Maven. Although there are some restrictions to that and we also will keep the PDE build as our primary build. The snapshot and release repository are located at http://repo.openscada.org/maven/ |
...