2.21 -> 2.22

See merge request !11

Issue-Ref: 4276
Issue-Url: af3#4276

Signed-off-by: Andreas Bayha <bayha@fortiss.org>

4229

See merge request !10

Issue-Ref: 4229 
Issue-Url: af3#4229

Signed-off-by: Andreas Bayha [bayha@fortiss.org](mailto:bayha@fortiss.org)

2.19 -> 2.20

See merge request !9

Issue-Ref: 4167

Signed-off-by: Johannes Eder <eder@fortiss.org>

2.18 -> 2.19

See merge request !8

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



Signed-off-by: Johannes Eder <eder@fortiss.org>

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

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



Signed-off-by: Johannes Eder <eder@fortiss.org>

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


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

* Self-contained version.
* Avoids triggering the build phase of the container module (product
  would be extracted twice).
* Fixes last failers of the CI build.

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

In the gitlab instance, it is more efficient and less error-prone (too
many files) to pass around the zipped product instead of the directory.

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

... This avoids triggering the copy job twice.

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

Only by copying the produced product and setting the test configuration
to "p2Installed", the efxclipse osgi extensions are activated on
startup. This is required to get JavaFX up and running. Due to a recent
code modification, JFX code is already loaded during startup such that
JavaFX is now also need.
The absence of JavaFX was not noticed before since no JFX classes were
loaded by kernel services, nor did any test require them.
In addition to fixing the initial bug, we are also testing the produced
build now and not only a subset.

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

3861: Remove deprecated plugins

See merge request !6

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



Signed-off-by: Simon Barner <barner@fortiss.org>

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

3773

See merge request !5

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


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

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


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

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


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

Conflicts:
	org.fortiss.af3.phoenix.product.tests/tests-src/org/fortiss/af3/phoenix/product/tests/AllTests.java

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

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


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

[3827] Update .gitignore and include the bin folder

See merge request !4

* Use the same .gitignore file as e.g. in the af3-rcp repository.

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



Signed-off-by: Tiziano Munaro <munaro@fortiss.org>

Release 2.15.0

See merge request !3

Issue-Ref: 3725
Signed-off-by: Hernan Ponce de Leon <ponce@fortiss.org>

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

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

Remove dependency upon deployment.ui

See merge request !1

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


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

... The parameters to launch AF3 are sufficient and correct now.

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>

* In order to run junit tests on the final product, we need to execute
  AF3 as a whole to ensure correct application startup.
* Add a unpack module that extracts the AF3 product to the work
  directory of the testing plugin.
* Move the testing definition to the tests/af3 folder and adjust the
  paramerters to launch AF3 correctly.

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>

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


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