...
| Repository | Branch |
|---|---|
| git://git.openscada.org/org.openscada.builder.git | 1.1 |
| git://git.openscada.org/org.openscada.external.git | 1.1 |
| git://git.openscada.org/org.openscada.aurora.git | 1.1 |
| git://git.openscada.org/org.openscada.oxygen.git | 1.1 |
| git://git.openscada.org/org.openscada.utgard.git | 1.1 |
| git://git.openscada.org/org.openscada.orilla.git | 1.1 |
| git://git.openscada.org/org.openscada.othala.git | 1.1 |
| git://git.openscada.org/org.openscada.dakara.git | 1.1 |
| git://git.openscada.org/org.openscada.infinity.git | 1.1 |
| git://git.openscada.org/org.openscada.orion.git | 1.1 |
| git://git.openscada.org/org.openscada.deploy.git | 1.1 |
The target environment
There are two ways to set up your target platform.
All manual
Create a new Target Environment (start with an empty one). To do this open the "Edit -> Preferences"
...
Instead of installing the modules via Software Site you can also download the P2 ZIP archives and install them using these.Note:
All automatic
As an alternative you can try the target platform definition in the project "builder_global". But please be aware of the fact that this is new and rarely tested. It will however be extended in the "1.1" branch and should become the default way to do it in the "1.1" release.
Note that when you set up your target platform with the ".target" file you will have your current running Eclipse as a base. This is not always a good idea, since you will have all tools which you have running inside your Eclipse also available for developing applications. While this sounds like a great idea at first, it not always is. One Eclipse acts as a development tool, the other as "target platform". That's why Eclipse makes a difference here.
Compile XMLBeans
Run the "build.xml" ant script from "builder_global".
...