Установка mvn mac os

How to install Maven on Mac OS

In this Post we will see How to install Maven on Mac OS. Maven is build tool primary for Java projects.

Prerequisites:

Maven is written in Java. Therefore, we need to have Java JDK installed on Mac OS. Java can be install from Oracle’s download website.

If you have to View How to install Java JDK on Mac OS X ( with JAVA_HOME ) the follow the Video instruction in https://youtu.be/y6szNJ4rMZ0

Maven Installation Steps:

Step 1 Download the Apache Maven bin.tar.gz file from http://maven.apache.org/download.cgi .
Extract/unzip the distribution archive file into /Applications/apache-maven-3.4.5 by the following command.

Step 2 Add the M2_HOME environment variable. To edit your

/.bash_profile, run the following command to open it in text editor.

Step 3 Add the following exports to your

/.bash_profile and save it.

Step 4 Use source command on

/.bash_profile which is used to load any functions file into the current shell script or a command prompt.

Step 5
Run the following command to verify maven version

If your Mac OS system displays information on the Apache Maven version installed, this means Maven is successfully installed on you Mac.

Video Instructions – How to install Maven on Mac

Источник

Maven on MacOS (OSX)

for Java, Jenkins, etc.

This describes how to install Maven using Homebrew, the configure and use it.

Ant was originally created (using Java) to replace the make utility for cross-platform use. With Ant, everything needs to be coded explictly in XML. Its files are difficult to reuse.

Unlike Ant, Maven also provides dependency management, standard project layout, and project management.

Mated with Java

Maven is written in Java, and grew up supporting Java builds by creating from Java source and resources for deployment deliverables like JAR file or WAR files.

Default in Jenkins

Maven is the default build tool in the Jenkins continuous integration tool to perform builds when code is committed.

Unlike shell script procedural code, Maven files enable declarative statements.

Maven adopts the principle of “Convention over configuration”, which means less coding work. However, it operates as a “black box”.

Install latest

PROTIP: Rather than downloading directly from https://maven.apache.org/download.cgi, use a package manager.

To install the latest version on MacOS:

the response I got on Dec 29, 2017:

Install previous version

Then, to switch among versions:

Configure Path

I got this response:

Confirm the path:

NOTE: Before OSX Mavericks, Maven was installed by default in:
/usr/share/maven/bin/mvn

Confirm the path. Substitute the version (3.5.2) with the version you just installed:

mvn files should be listed:

Open using a text editor, substituting subl (for Sublime) with atom or vim:

Add the following to under export PATH=, changing the version (3.5.2) to whatever appears above:

On Windows, define environment variable M2_HOME with a path such as:

Within environment variable PATH , add:

View changed environment variables. On a Mac:

The response if installed by Homebrew on Mac:
/usr/local/Cellar/maven/3.5.2/libexec

The response if installed by Homebrew on Mac:
/usr/local/Cellar/maven/3.5.2/libexec/bin

In a Terminal, verify changes:

The reply is, for example:

Change Default Configurations

Navigate to the hidden folder Maven installed to house packages installed (junit, commons-cli, commons-lang, etc).

Some prefer to change Maven’s local repository to another location.

There is a settings.xml file containing:

Using Maven

Maven allows use of a central maven repository.

The pom.xml (Project Object Model) file describes project dependencies which Maven resolves by downloading them.

NOTE: Some prefer to install and use the Cargo plugin (from Codehaus) to Maven in order to eliminate use of pom.xml. In a folder that contains a pom.xml:

mvn clean verify org.codehaus.cargo:cargo-maven2-plugin:run

The vast majority of Maven-built projects can be built with this command:

The “clean” cleans out results from the prior build before starting with install.

During the first full run, testing jars are installed in your local maven repository.

Maven is said to also act as project management tool because it can generate reports etc.

build.xml

Maven enforces a standard naming convention for artifacts defined using groupId, artifactId, and version.

After the first run, builds can skip tests with this additional parameter:

Maven lifecycle phases

Here are sub-commands for mvn:

Sub-command	Description
validate	Validate the project is correct and all necessary information is available
initialize	initialize build state, (for example : set properties, create directories,… etc)
generate-sources	generate any source code for inclusion in compilation
process-sources	process the source code (for example : filter any values)
generate-resources	generate resources for inclusion in the package.
process-resources	copy and process the resources into the destination directory, ready for packaging.
compile	compile the source code of the project.
process-classes	post-process the generated files from compilation (for example : to do bytecode enhancement on Java classes)
generate-test-sources	generate any test source code for inclusion in compilation.
process-test-sources	process the test source code (for example : to filter any values)
generate-test-resources	create resources for testing.
process-test-resources	copy and process the resources into the test destination directory.
test-compile	compile the test source code into the test destination directory.
process-test-classes	post-process the generated files from test compilation (for example : to do bytecode enhancement on Java classes)
test	run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed.
prepare-package	perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package.
package	Take the compiled code and package it in its distributable format (for example : jar, war, …etc)
pre-integration-test	perform actions required before integration tests are executed. This may involve things such as setting up the required environment.
integration-test	process and deploy the package if necessary into an environment where integration tests can be run.
post-integration-test	perform actions required after integration tests have been executed. This may including cleaning up the environment.
verify	run any checks to verify the package is valid and meets quality criteria.
install	install the package into the local repository, for use as a dependency in other projects locally.
deploy	done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.

Sub-command	Description
pre-clean	Executes processes needed prior to the actual project cleaning
clean	Remove all files generated by the previous build
post-clean	Execute processes needed to finalize the project cleaning

Sub-command	Description
pre-site	Executes processes needed prior to the actual project site generation.
site	Generates the project’s site documentation.
post-site	Executes processes needed to finalize the site generation, and to prepare for site deployment.
site-deploy	Deploys the generated site documentation to the specified web server.

Maven plug-in goals by lifecycle phase

Each unit of execution work in Maven is called a goal.

Maven C/C++ Plugin http://duns.github.io/maven-nar-plugin/

Maven plug-ins by lifecycle phase

The graphic at Empeccableweb includes “Archetype”:

Dependencies

Mirror

The Maven Central Repository provides a UI to
the mirror website where Maven pulls files from. In the US it is:

Источник

Maven on MacOS (OSX)

for Java, Jenkins, etc.

This describes how to install Maven using Homebrew, the configure and use it.

Ant was originally created (using Java) to replace the make utility for cross-platform use. With Ant, everything needs to be coded explictly in XML. Its files are difficult to reuse.

Unlike Ant, Maven also provides dependency management, standard project layout, and project management.

Mated with Java

Maven is written in Java, and grew up supporting Java builds by creating from Java source and resources for deployment deliverables like JAR file or WAR files.

Default in Jenkins

Maven is the default build tool in the Jenkins continuous integration tool to perform builds when code is committed.

Unlike shell script procedural code, Maven files enable declarative statements.

Maven adopts the principle of “Convention over configuration”, which means less coding work. However, it operates as a “black box”.

Install latest

PROTIP: Rather than downloading directly from https://maven.apache.org/download.cgi, use a package manager.

To install the latest version on MacOS:

the response I got on Dec 29, 2017:

Install previous version

Then, to switch among versions:

Configure Path

I got this response:

Confirm the path:

NOTE: Before OSX Mavericks, Maven was installed by default in:
/usr/share/maven/bin/mvn

Confirm the path. Substitute the version (3.5.2) with the version you just installed:

mvn files should be listed:

Open using a text editor, substituting subl (for Sublime) with atom or vim:

Add the following to under export PATH=, changing the version (3.5.2) to whatever appears above:

On Windows, define environment variable M2_HOME with a path such as:

Within environment variable PATH , add:

View changed environment variables. On a Mac:

The response if installed by Homebrew on Mac:
/usr/local/Cellar/maven/3.5.2/libexec

The response if installed by Homebrew on Mac:
/usr/local/Cellar/maven/3.5.2/libexec/bin

In a Terminal, verify changes:

The reply is, for example:

Change Default Configurations

Navigate to the hidden folder Maven installed to house packages installed (junit, commons-cli, commons-lang, etc).

Some prefer to change Maven’s local repository to another location.

There is a settings.xml file containing:

Using Maven

Maven allows use of a central maven repository.

The pom.xml (Project Object Model) file describes project dependencies which Maven resolves by downloading them.

NOTE: Some prefer to install and use the Cargo plugin (from Codehaus) to Maven in order to eliminate use of pom.xml. In a folder that contains a pom.xml:

mvn clean verify org.codehaus.cargo:cargo-maven2-plugin:run

The vast majority of Maven-built projects can be built with this command:

The “clean” cleans out results from the prior build before starting with install.

During the first full run, testing jars are installed in your local maven repository.

Maven is said to also act as project management tool because it can generate reports etc.

build.xml

Maven enforces a standard naming convention for artifacts defined using groupId, artifactId, and version.

After the first run, builds can skip tests with this additional parameter:

Maven lifecycle phases

Here are sub-commands for mvn:

Sub-command	Description
validate	Validate the project is correct and all necessary information is available
initialize	initialize build state, (for example : set properties, create directories,… etc)
generate-sources	generate any source code for inclusion in compilation
process-sources	process the source code (for example : filter any values)
generate-resources	generate resources for inclusion in the package.
process-resources	copy and process the resources into the destination directory, ready for packaging.
compile	compile the source code of the project.
process-classes	post-process the generated files from compilation (for example : to do bytecode enhancement on Java classes)
generate-test-sources	generate any test source code for inclusion in compilation.
process-test-sources	process the test source code (for example : to filter any values)
generate-test-resources	create resources for testing.
process-test-resources	copy and process the resources into the test destination directory.
test-compile	compile the test source code into the test destination directory.
process-test-classes	post-process the generated files from test compilation (for example : to do bytecode enhancement on Java classes)
test	run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed.
prepare-package	perform any operations necessary to prepare a package before the actual packaging. This often results in an unpacked, processed version of the package.
package	Take the compiled code and package it in its distributable format (for example : jar, war, …etc)
pre-integration-test	perform actions required before integration tests are executed. This may involve things such as setting up the required environment.
integration-test	process and deploy the package if necessary into an environment where integration tests can be run.
post-integration-test	perform actions required after integration tests have been executed. This may including cleaning up the environment.
verify	run any checks to verify the package is valid and meets quality criteria.
install	install the package into the local repository, for use as a dependency in other projects locally.
deploy	done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.

Sub-command	Description
pre-clean	Executes processes needed prior to the actual project cleaning
clean	Remove all files generated by the previous build
post-clean	Execute processes needed to finalize the project cleaning

Sub-command	Description
pre-site	Executes processes needed prior to the actual project site generation.
site	Generates the project’s site documentation.
post-site	Executes processes needed to finalize the site generation, and to prepare for site deployment.
site-deploy	Deploys the generated site documentation to the specified web server.

Maven plug-in goals by lifecycle phase

Each unit of execution work in Maven is called a goal.

Maven C/C++ Plugin http://duns.github.io/maven-nar-plugin/

Maven plug-ins by lifecycle phase

The graphic at Empeccableweb includes “Archetype”:

Dependencies

Mirror

The Maven Central Repository provides a UI to
the mirror website where Maven pulls files from. In the US it is:

Источник