Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: spelling fix


Users and developers familiar with the conventional Make target install might cringe at that mvn invocation, but the install phase in Maven is not at all like the target by that name typically found in a Makefile. In fact, Maven does not have a build phase that maps to the functionality typically performed by make install (and I have never seen such functionality kludged into a Maven build). This is one of the areas where the intended audiences of the tool tools diverge; make install is (typically, but not necessarily) intended for sysadmins actually installing software on a system for use by end-users, whereas mvn install is typically done by a developer working in his home directory, and simply copies the current build artifact beneath a special directory (${HOME}/.m2/repsoitory/...) that will be queried by other Maven builds that declare a dependency on the artifact.