Difference Between Install and Package in Maven
Explore the difference between install and package in Maven. Learn what each phase does, when to run mvn package vs mvn install, and how these steps affect the local repository and multi-module builds.
In Maven, the difference between install and package in maven hinges on what Maven does with the built artifact. Running mvn package produces the distributable artifact (jar/war) in the project’s target directory. Running mvn install not only builds the artifact but also copies it into your local Maven repository, making it available to other projects on the same machine. This distinction guides when to use each command.
The difference between install and package in Maven: An overview
The phrase the difference between install and package in maven describes two distinct goals in Maven's lifecycle. At its core, Maven package creates a portable artifact (like a JAR or WAR) that can be distributed or deployed. In contrast, Maven install goes one step further by placing that artifact into your local repository, typically under ~/.m2/repository, so other projects on the same machine can declare it as a dependency. This distinction matters for local development, multi-module builds, and CI workflows. Throughout this article we will repeatedly reference the phrase difference between install and package in maven to illustrate how each phase impacts artifacts, repositories, and project structure. When you consider the difference between install and package in maven, you should map your workflow to whether you need a reusable artifact inside your local development environment or a distributable file ready for packaging and distribution.
In practice, the difference between install and package in maven is most obvious during multi-module builds. A module that produces a library or component and is used by other modules often benefits from being installed into the local repository so dependent modules can resolve it without publishing to a remote repository. If you only care about generating a binary as an output file for testing or distribution, the package phase suffices. The Install Manual team emphasizes aligning your commands with your target deliverable: package for artifact generation, install for local reuse, and deploy for sharing with remote repositories. This framing helps reduce confusion and keeps your build consistent across environments.
The difference between install and package in maven also has implications for CI pipelines. In continuous integration, you typically run mvn package to ensure a clean, repeatable build that outputs a ready-to-distribute artifact. If your pipeline includes a subsequent step that aggregates artifacts for other projects on runners or developers, you might insert mvn install to populate the local repository, enabling downstream builds to pick up the artifact without manual publishing. Understanding this distinction—what the artifact is, where it goes, and how other projects will access it—clarifies the boundaries between building, packaging, and sharing in Maven workflows.
The difference between install and package in Maven: An overview
The phrase the difference between install and package in maven describes two distinct goals in Maven's lifecycle. At its core, Maven package creates a portable artifact (like a JAR or WAR) that can be distributed or deployed. In contrast, Maven install goes one step further by placing that artifact into your local repository, typically under ~/.m2/repository, so other projects on the same machine can declare it as a dependency. This distinction matters for local development, multi-module builds, and CI workflows. Throughout this article we will repeatedly reference the phrase difference between install and package in maven to illustrate how each phase impacts artifacts, repositories, and project structure. When you consider the difference between install and package in maven, you should map your workflow to whether you need a reusable artifact inside your local development environment or a distributable file ready for packaging and distribution.
In practice, the difference between install and package in maven is most obvious during multi-module builds. A module that produces a library or component and is used by other modules often benefits from being installed into the local repository so dependent modules can resolve it without publishing to a remote repository. If you only care about generating a binary as an output file for testing or distribution, the package phase suffices. The Install Manual team emphasizes aligning your commands with your target deliverable: package for artifact generation, install for local reuse, and deploy for sharing with remote repositories. This framing helps reduce confusion and keeps your build consistent across environments.
The difference between install and package in maven also has implications for CI pipelines. In continuous integration, you typically run mvn package to ensure a clean, repeatable build that outputs a ready-to-distribute artifact. If your pipeline includes a subsequent step that aggregates artifacts for other projects on runners or developers, you might insert mvn install to populate the local repository, enabling downstream builds to pick up the artifact without manual publishing. Understanding this distinction—what the artifact is, where it goes, and how other projects will access it—clarifies the boundaries between building, packaging, and sharing in Maven workflows.
Comparison
| Feature | Package phase | Install phase |
|---|---|---|
| Artifact output | Distributable artifact (jar/war) created in target/ | Artifact copied to local repository (~/.m2/repository) |
| Local repository impact | No changes to local repo beyond potential packaging metadata | Local repo updated to include the artifact for reuse by other projects |
| Typical command | mvn package | mvn install |
| Best for | Creating distributable artifacts for deployment or distribution | Enabling local multi-module builds and reuse by dependent projects |
| Remote deployment | Not performed by package; requires separate deploy step | Not performed by install; typically followed by deploy for remote sharing |
Positives
- Package yields a ready-to-distribute artifact suitable for sharing
- Install enables reusability by other local projects
- Clear separation of concerns between building and sharing
- Supports efficient multi-module development workflows
- Fits standard Maven lifecycle without extra steps
Disadvantages
- Installing too frequently can clutter the local repository
- Relying on install in CI without remote deployment can hinder collaboration
- Package alone does not prepare artifacts for reuse in other projects
Package for artifact creation; install for local reuse
For most workflows, use mvn package to produce distributables. Use mvn install when you want downstream modules on the same machine to resolve the artifact without publishing remotely. Reserve deploy for pushing artifacts to remote repositories.
Got Questions?
What is the practical difference between install and package in Maven?
The practical difference between install and package in Maven is that package produces a distributable artifact, while install adds the artifact to the local repository for reuse by other projects. This distinction affects how you share artifacts in multi-module builds.
Package builds the artifact; install makes it available locally for other projects.
When should I run mvn package instead of mvn install?
Run mvn package when you need a distributable artifact for testing, distribution, or packaging. If no downstream local reuse is required, package is sufficient and simpler.
Use package to create the artifact; install only if you need it in your local repo.
Will mvn install work in a CI environment where artifacts are built?
In a CI environment, you can perform mvn install if the build includes downstream modules that rely on the local repository. Otherwise, mvn package followed by explicit deployment may be more appropriate.
Install is useful when later steps reuse the artifact in the same environment.
Can I run both package and install in a single build?
Yes, you can run a sequence like mvn package then mvn install in a multi-module project. This yields both a distributable artifact and a local repo entry for dependent modules.
You can chain package and install to produce artifacts and populate the local repo.
Do I need to deploy to a remote repository for collaboration?
For collaboration across teams, deploying to a remote repository (via mvn deploy) is typically required. The install phase does not publish remotely by itself.
Deploy to a remote repo for sharing with others; install stays local.
How does the local repository impact other projects?
The local repository acts as a cache and source of truth for artifacts used by multiple projects on the same machine. Installing artifacts there enables downstream modules to resolve dependencies automatically.
Artifacts in ~/.m2/repository are shared by projects on your machine.
Main Points
- Understand Maven lifecycles to pick the right command
- Package creates distributable artifacts like jars or wars
- Install places artifacts into the local repository for reuse
- Use deploy to publish to remote repositories
- Keep CI/CD workflows consistent with a single build strategy
