etc, ci: Use --workspace option for supported cargo commands

The option have been stable on Cargo since 1.40.0, replacing `--all`.

Author: behnam

.appveyor.yml

@@ -23,7 +23,7 @@ environment:
     CARGO_HTTP_CHECK_REVOKE: false
 
 test_script:
-  - cargo build --verbose --all
-  - cargo doc   --verbose --all --no-deps
+  - cargo build --verbose --workspace
+  - cargo doc   --verbose --workspace --no-deps
 
-  - cargo test  --verbose --all
+  - cargo test  --verbose --workspace

.travis.yml

@@ -26,18 +26,18 @@ env:
     - RUST_BACKTRACE=full
 
 script:
-  - cargo build --verbose --all
-  - cargo doc   --verbose --all --no-deps
+  - cargo build --verbose --workspace
+  - cargo doc   --verbose --workspace --no-deps
 
-  - cargo test  --verbose --all
+  - cargo test  --verbose --workspace
 
   #  unic-ucd-normal is used in unic-ucd with non-default feature
   - cargo test  --verbose --manifest-path unic/ucd/normal/Cargo.toml
 
   # == Nightly-only ==
 
   - test "$TRAVIS_RUST_VERSION" != "nightly" ||
-    cargo test  --verbose --all --all-features
+    cargo test  --verbose --workspace --all-features
 
 # TODO: - rustdoc --test README.md -L target/debug -L target/debug/deps
 

etc/cargo-clippy-all.sh

@@ -10,8 +10,8 @@
 # option. This file may not be copied, modified, or distributed
 # except according to those terms.
 
-# Since `cargo publish --all` does not exist yet, we use this dumb alternative
-# solution for now.
+# Since `cargo clippy --workspace` does not exist yet, we use this dumb
+# alternative solution for now.
 #
 # Main downside of this approch is that there are separate `target/`
 # directories used for each component, increasing the test and publish process

etc/cargo-package-all.sh

@@ -10,8 +10,8 @@
 # option. This file may not be copied, modified, or distributed
 # except according to those terms.
 
-# Since `cargo package --all` does not exist yet, we use this dumb alternative
-# solution for now.
+# Since `cargo package --workspace` does not exist yet, we use this dumb
+# alternative solution for now.
 #
 # Main downside of this approch is that there are separate `target/`
 # directories used for each component, increasing the test and publish process

etc/cargo-publish-all.sh

@@ -10,8 +10,8 @@
 # option. This file may not be copied, modified, or distributed
 # except according to those terms.
 
-# Since `cargo publish --all` does not exist yet, we use this dumb alternative
-# solution for now.
+# Since `cargo publish --workspaces` does not exist yet, we use this dumb
+# alternative solution for now.
 #
 # Main downside of this approch is that there are separate `target/`
 # directories used for each component, increasing the test and publish process

etc/cargo-test-all.sh

@@ -10,8 +10,9 @@
 # option. This file may not be copied, modified, or distributed
 # except according to those terms.
 
-# Since `cargo publish --all` does not exist yet, we use this dumb alternative
-# solution for now.
+# Since `cargo publish --workspace` does not exist yet, we use this dumb
+# alternative solution for now to test all components in their isolated form,
+# before publishing them.
 #
 # Main downside of this approch is that there are separate `target/`
 # directories used for each component, increasing the test and publish process