Compiling transforms source code into another representation. A build can also resolve dependencies, run tests, and package an artifact. An IDE helps you write and inspect code; Maven and Gradle automate build work. When an error appears, identify which stage failed before blaming the tool named in the message.
Key terms
Compilation transforms code; a build organizes that and other steps into an output. Maven and Gradle can automate the workflow.
| Term | Meaning |
|---|---|
compile | Translate source code into another representation, such as machine code, bytecode, or an intermediate form, while preserving the intended program behavior. |
IDE | Integrated development environment: a tool that combines facilities such as an editor, code navigation, debugging, and build or run integration. |
Cross platform | Describes software or a technology intended to work across more than one operating-system or device environment. Actual compatibility depends on supported targets. |
preprocessing | Preparatory transformation of raw input before the main processing step, such as cleaning and shaping data before analysis. The exact operations depend on the workflow. |
Ant | Apache Ant, a Java-based build tool that defines tasks and dependencies, commonly in XML build files. It is often encountered in existing projects and build-tool history. |
Terms to distinguish
| Term | Meaning |
|---|---|
Maven | A build and project-management tool that uses a project object model, conventions, and plugins to organize tasks such as dependency resolution, compilation, testing, and packaging. |
Gradle | A build automation tool that defines and runs task graphs, manages dependencies, and supports JVM, Android, and other project types. |
Groovy | A programming language for the JVM, often encountered in Gradle build scripts and other Java ecosystem work. |
XML | Extensible Markup Language, a text format for structured data and markup defined through nested elements and attributes. |
Interface | A boundary or contract through which two components or systems interact, including the operations and rules they expose to each other. |
Terms in code
| Term | Meaning |
|---|---|
Build | The process of turning source and dependencies into a tested or packaged software output; the word can also mean the resulting artifact. |
Script Language | A language often run through an interpreter or runtime rather than as a separately produced executable. Implementations may still compile to bytecode or use JIT compilation. |
JavaScript | A programming language used for interactive web pages and also in server-side and other runtimes. It is not limited to browser scripts. |
Reading a technical document
Compilation can be one part of a build; dependency resolution, tests, and packaging may surround it.
When a build fails, check whether the problem is compilation, a missing dependency, a failed test, or packaging. The Maven introduction describes how its model and plugins organize these stages. Knowing the stage is more useful than treating every tool name as the cause.
Key takeaways
Separate editing, transformation, dependency management, and artifact creation.
- compile — Transforms source into another executable or intermediate representation.
- Gradle — Automates build tasks and dependencies across project types.
- JavaScript — Runs in browsers and other runtimes, including servers.
