テーマ： build-tools

• Cargo、クレート、エディション：Rust プロジェクトのビルドとバージョン管理

  Cargo は Cargo.toml からクレートをビルドし、SemVer 互換範囲の依存関係を解決して Cargo.lock に記録します。一つのビルドに同じクレートの互換性のない二つのメジャーバージョンを含められます。エディションはクレートごとに任意で選ぶ相互運用可能な言語バージョンなので、変更しても依存する側に追従を強制しません。

  article · ja · reviewed · 知識の基準日 2026-09-16

• Maven versus Gradle: what a newcomer needs to build someone else's JVM project

  Maven describes a project declaratively in pom.xml and runs fixed lifecycle phases (validate, compile, test, package, verify, install, deploy) with plugin goals bound to them; Gradle runs a graph of tasks configured by build.gradle(.kts) scripts and plugins. Both resolve transitive dependencies but with different conflict rules (Maven: nearest definition; Gradle: highest version), and both ship a wrapper script that pins the build tool version.

  article · en · reviewed · 知識の基準日 2026-09-16

• make as a task runner: phony targets, tabs and one shell per line

  A Makefile is a workable entry point for a repository's commands if command targets are declared .PHONY, recipe lines start with a tab, and it is understood that each recipe line runs in its own shell unless .ONESHELL is set; keep the default goal harmless and keep real file dependencies real.

  article · en · reviewed · 知識の基準日 2026-09-16

• Pinning NuGet dependencies: PackageReference, central package management and packages.lock.json

  NuGet resolves the lowest applicable version of each package at restore time, so a restore can drift when new versions or floating ranges appear; a repeatable build declares versions once in Directory.Packages.props, enables RestorePackagesWithLockFile so packages.lock.json records the full closure, commits the lock file for applications, and restores with --locked-mode in CI.

  methodology · en · reviewed · 知識の基準日 2026-09-16

機械可読： JSON