...
Build and generate Eclipse files (the conservative method):.
For master - without using local maven repository;master – without using a local Maven repository:
Code Block | ||
---|---|---|
| ||
$ mkdir workspace $ cd workspace $ git clone https://github.com/apache/hive.git $ cd hive $ mvn clean package eclipse:clean eclipse:eclipse -Pitests -DskipTests -DdownloadSources -DdownloadJavadocs |
NOTE: The presence of the package target is crucial in sucessfully successfully generating the project files.
NOTE: I would also recommend It is recommended to wipe out or rename the org/apache/hive subtree of the local m2 repo repository prior to generating the project files; and you may want to check after its execution that it does not contain any files - if – if it does contain something; , then your project files may not be fully independent of downloaded maven Maven artifacts.
This will work on all branches; but keep in mind that in this case you are installing the hive Hive artifacts into your local repository.
...
It would be great to have it connected, but it would make it harder to use mvn test locally. The best option would be to utilize the failsafe plugin for integration testing; but it needs a bit different setup, and its it's harder to use for now.... If you'd like to give that a try, by all means, go ahead.
There is an option to attach all the itest subprojects to the main project by enabling this with -Pitests (HIVE-13490).
There are some good and bad sides using this, it's introduced as a profile to clearly communicate that the integration tests are attached to the main project.
The good side is that you may use freely use -Pitests to run integration tests from the root project without the need of mvn install.
Code Block | ||
---|---|---|
| ||
mvn test -q -Pitests -Dtest=TestCliDriver -Dqtest=sample2.q |
And by having -Pitests around you are always compiling the integrations tests to...this can improve compile time error detection.
The bad thing side is that a simple mvn test -Pitests will start executing all integration tests.
Why does a test fail with a NullPointerException in MiniDFSCluster?
...