Issue-Ref: 3721
Issue-Url: https://af3-developer.fortiss.org/issues/3721


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3337
Issue-Url: https://af3-developer.fortiss.org/issues/3337


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Signed-off-by: Alexander Diewald <diewald@fortiss.org>

... include it as a submodule.

Issue-Ref: 3620
Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* Activate each profile with environment switches.
* Environment properties allow for more flexibility than pure profile
  definitions since they allow negation, querying values etc.

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* To be triggered with the profile "tests".
* Launch the EMF generator only with the profiles "af3" or "tooling".
* Add the AF3 tests as a submodule.

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

On jenkins they will be build separately such that other build jobs
can reuse the artifacts of the kernel build.

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

* TODO: Tests missing.
* AF3 product starts (on windows).
* Remove platform specific features from the feature.xml.
  TODO: Probably, all other non-AF3 tooling/kernel plugins can be
  removed as well, since they are only needed and added automatically
  when building the product.
  TODO: Create a tooling feature.
* Add a product definition for AF3 Phoenix.
* Use felix instead of equinox.ds in the start config of the product.
  (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=538737 )
* Add a maven module that issues the code generation from EMF models.
* Move the OpenJFX stubs to the common bundle pom such that these libs
  are only acquired when building sources.

Issue-Ref: 3620
Issue-Url: https://af3-developer.fortiss.org/issues/3620


Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Signed-off-by: Alexander Diewald <diewald@fortiss.org>

Signed-off-by: Alexander Diewald <diewald@fortiss.org>