0b581f9ffe
horizon-client, horizon-world and horizon-protocol each had an example named `probe`. Cargo copies every crate's examples into one <profile>/examples/ directory, so parallel parity harnesses sharing a target dir could run another crate's probe (CI parity run 40055656303: command_parse ran the horizon-world dispatcher). The examples are now client_probe, world_probe and protocol_probe ([[example]] in each Cargo.toml; the files stay where they are), and every harness builds and runs its own crate's name. tools/parity.py recognises the new names when it counts the probes a harness ran, and renames the old `probe` in recorded artifacts to the crate's target (from the record's -p, else its probe sources), so the prebuild still builds them instead of dropping them as unknown. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
27 lines
810 B
TOML
27 lines
810 B
TOML
[package]
|
|
name = "horizon-protocol"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
rust-version.workspace = true
|
|
description = "Horizon's Minecraft Java Edition 26.3 network protocol (version 777)"
|
|
|
|
[dependencies]
|
|
horizon-core = { path = "../horizon-core" }
|
|
horizon-world = { path = "../horizon-world" }
|
|
flate2 = { version = "1.1.10", default-features = false, features = ["zlib-rs", "runtime_detection"] }
|
|
serde_json = "1.0.151"
|
|
# The shared secret and RSA padding (OS randomness) and the server hash.
|
|
getrandom = "0.3"
|
|
sha1 = "0.10"
|
|
# Secure chat: SHA256withRSA message signatures.
|
|
sha2 = "0.10"
|
|
|
|
# Its own name, not `probe`: Cargo copies every crate's examples into one target/<profile>/examples.
|
|
[[example]]
|
|
name = "protocol_probe"
|
|
path = "examples/probe.rs"
|
|
|
|
[lints]
|
|
workspace = true
|