Understanding Project Structure

Clojure projects look simple on disk, but there are a few conventions that are worth learning early. Once you can glance at a repository and predict where a namespace lives, you will read code much faster.

The conventions that matter

• src/ holds production code; test/ holds tests; resources/ holds classpath resources.
• A namespace maps to a file path, roughly like a Java package maps to a directory.
• Hyphens in namespace segments become underscores in file names (my-app.core -> my_app/core.clj).

Java mental model: namespaces are not classes, but the “package-to-path” navigation skill transfers almost directly.

This section gives you the minimum structure you need to follow real projects and avoid “where is this code actually loaded from?” confusion.

In this section

• Clojure Namespaces and Files: A Comprehensive Guide for Java Developers
  Explore how Clojure uses namespaces to organize code, including namespace declaration with `ns` and the correspondence between namespaces and file paths.
• Source and Test Directories in Clojure Projects
  Explore the importance of separating source and test directories in Clojure projects, drawing parallels with Java practices, and learn how to organize your Clojure project structure effectively.
• Configuration Files in Clojure: Mastering project.clj and deps.edn
  Explore the intricacies of configuration files in Clojure, focusing on project.clj, deps.edn, and profiles.clj for managing dependencies and environment-specific settings.