Merge branch 'storm-3253-deprecate-storm-repl' of https://github.com/d2r/storm
STORM-3253: Deprecates the storm repl subcommand This closes #2875 Project: http://git-wip-us.apache.org/repos/asf/storm/repo Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/c52cedf9 Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/c52cedf9 Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/c52cedf9 Branch: refs/heads/master Commit: c52cedf9bd7430ef7fb47279b232ca4d769e64f0 Parents: 8e1627d 8533116 Author: Robert Evans <ev...@yahoo-inc.com> Authored: Mon Oct 15 08:51:22 2018 -0500 Committer: Robert Evans <ev...@yahoo-inc.com> Committed: Mon Oct 15 08:51:22 2018 -0500 ---------------------------------------------------------------------- DEVELOPER.md | 8 -------- bin/storm.py | 3 ++- docs/Command-line-client.md | 2 ++ 3 files changed, 4 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/storm/blob/c52cedf9/DEVELOPER.md ---------------------------------------------------------------------- diff --cc DEVELOPER.md index e4da377,4e595eb..20ac51f --- a/DEVELOPER.md +++ b/DEVELOPER.md @@@ -292,20 -292,12 +292,12 @@@ To run all unit tests plus Clojure inte To run all unit tests and all integration tests execute one of the commands - mvn -P all-tests verify - mvn -P all-tests integration-test + mvn -P all-tests,examples,externals verify + mvn -P all-tests,examples,externals integration-test - You can also run tests selectively via the Clojure REPL. The following example runs the tests in - [auth_test.clj](storm-core/test/clj/org/apache/storm/security/auth/auth_test.clj), which has the namespace - `org.apache.storm.security.auth.auth-test`. - You can also run tests selectively with `-Dtest=<test_name>`. This works for both clojure and junit tests. - > Tip: IDEs such as IntelliJ IDEA support a built-in Clojure REPL, which you can also use to run tests selectively. - > Sometimes you may find that tests pass/fail depending on which REPL you use, which -- although frustrating -- - > can be helpful to narrow down errors. - Unfortunately you might experience failures in clojure tests which are wrapped in the `maven-clojure-plugin` and thus doesn't provide too much useful output at first sight - you might end up with a maven test failure with an error message as unhelpful as `Clojure failed.`. In this case it's recommended to look into `target/test-reports` of the failed project to see what actual tests have failed or scroll through the maven output looking for obvious issues like missing binaries. By default integration tests are not run in the test phase. To run Java and Clojure integration tests you must enable the profile
