Hi Greg,
With Maven it should also work.
For the compiler:
If you do a “mvn clean install” it should run almost all unit-tests and
integration-tests.
If you define an Evironment variable FLASHPLAYER_DEBUGGER (Same as for the ANT
build) pointing to the flash debug player the integration-tests with Flash
should work.
For the typedefs:
They don’t have tests (at least in Maven)
For the framework:
A simple “mvn clean install” compiles just the framework libs, but doesn’t
build the examples.
If you do a “mvn clean install –P build-examples” it will also build the
examples (Examples will run a small unit test that tests, the build artifacts
are correctly created)
If you do a “mvn clean install –P build-distribution” it will also build the
distribution (but not the examples)
If you do a “mvn clean install –P build-examples,build-distribution” it will
build the libs, examples and distribution.
And If you also define an environment variable “webdriver.gecko.driver” to the
selenium gecko-driver and run “mvn clean install –P build-examples” the build
will also run some browser-tests.
Chris
Am 03.03.17, 05:59 schrieb "Greg Dove" <gregd...@apache.org>:
There are a few things I have not yet gotten working so far, and the ant
checkintests is one of them.
If I understand correctly I should be running this before any commit? I
tried to make sense of this today, but it is not so easy (for me) because I am
unfamiliar with this stuff.
As I have never done this so far, is it ok if I just continue to commit
based on the regular ant and maven builds (with their various tests) completing
successfully? Otherwise if I need to get this set up, is there a guide to doing
so somewhere that I can follow?
