This closes #12907

Before, this was relying on .version.properties being available in the
flink-dist jar. This was not the case when building from a Flink source
release.

This is fixed by introducing a fake lib package that we place in the
lib/ folder to test the classloader resolution order. Both the lib
package and the user package contain a parent-child-test.properties and
we check the resolution order in the test.

Also change the test to not use TaskManager anymore.

This test was relying on TaskManager being present in Flink, this might
not be the case in the future. We change this test to place a fake class
in the "lib" package and the "user" package to make it independent of
the rest of Flink.

This closes #5813.

This closes #5717.

This also adds an end-to-end test that verifies correct order for both
classes and resources.

This closes #4503.

This closes #4384.

Use scala.binary.version as defined in the parent POM and remove the
script to swap scala version identifiers.

This closes #3800

This closes #2324

Makes the JUnit test utils (TestLogger, retry rules, ...) properly available to
other projects without the 'flink-core' test-jar, via the 'flink-test-utils-junit' project.

Makes the ForkableMiniCluster, TestEnvironment,  and other test utilities available in the 'main'
scope of the 'flink-test-utils' project.

Creates a 'flink-test-utils-parent' project that holds the 'flink-test-utils-junit' and
'flink-test-utils' project.

Also moves some tests between projects and inlines some very simple utility functions in
order to simplify some test jar dependencies.

- add suffixes
- adapt change-scala-version script

This closes #1529.

0.10-SNAPSHOT continues on branch release-0.10

[FLINK-2521] [tests] Adds TestLogger class which automatically logs the currently executed test names and the reasons for a failure.

Makes test bases extend TestLogger to add automatic test name logging

Frames test logging statements to make them more prominent

This closes #1015.

Closes #851

With this change, users can submit a Flink job to a YARN cluster without having a local client monitoring the Application Master or job. You can basically fire and forget a Flink job to YARN.
For supporting this, the ApplicationMaster can now monitor the status of a job and shutdown itself once it is in a terminal state.

The change also verifies that various ways of setting the parallelism on YARN are passed through the system correctly (per job, session).

There was a bug in YARN container creation which made the configuration values for the heap offset useless. This change fixes this error.

All mentioned features and bugs are covered by the flink-yarn-tests.

This closes #542

This closes #454

Removed Disclaimer file
Eliminated unnecessary incubating substrings
Bumped version to 0.9-SNAPSHOT

Replacing the EventCollector and the MemoryArchivist.

Finished EventCollector and adjusted ExecutionGraph and ExecutionVertex to register actors as listeners.

- Clean dependencies in flink-streaming connectors

- update _config.yaml of integrated documentation
- quick check on the quickstarts / build instructions to match the latest release
- quickstart.sh scrips now point to the correct versions.