Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

#### Maven

• 1
• 2
• 3

3.8.7 | Updated: 31 Dec 2022

858,282

23,279

Maintainer(s):

Software Author(s):

• The Apache Maven team
• 1
• 2
• 3

### All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

### Deployment Method: Individual Install, Upgrade, & Uninstall

To install Maven, run the following command from the command line or from PowerShell:

>

To upgrade Maven, run the following command from the command line or from PowerShell:

>

To uninstall Maven, run the following command from the command line or from PowerShell:

>
NOTE

This applies to both open source and commercial editions of Chocolatey.

### 1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

#### 1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

#### 2. Get the package into your environment

• Open Source or Commercial:
• Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
• You can also just download the package and push it to a repository

choco upgrade maven -y --source="'INTERNAL REPO URL'" [other options]

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade maven -y --source="'INTERNAL REPO URL'"
$exitCode =$LASTEXITCODE

Write-Verbose "Exit code was $exitCode"$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains$exitCode) {
Exit 0
}

Exit $exitCode - name: Install maven win_chocolatey: name: maven version: '3.8.7' source: INTERNAL REPO URL state: present chocolatey_package 'maven' do action :install source 'INTERNAL REPO URL' version '3.8.7' end cChocoPackageInstaller maven { Name = "maven" Version = "3.8.7" Source = "INTERNAL REPO URL" } Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco. package { 'maven': ensure => '3.8.7', provider => 'chocolatey', source => 'INTERNAL REPO URL', } Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey. ### 4. If applicable - Chocolatey configuration/installation See infrastructure management matrix for Chocolatey configuration elements and examples. Package Approved This package was approved as a trusted package on 31 Dec 2022. Description Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information Please Note: This is an automatically updated package. If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly. apache-maven-3.8.7\LICENSE apache-maven-3.8.7\NOTICE apache-maven-3.8.7\README.txt Apache Maven What is it? ----------- Maven is a software project management and comprehension tool. Based on the concept of a Project Object Model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. Documentation ------------- The most up-to-date documentation can be found at https://maven.apache.org/. Release Notes ------------- The full list of changes can be found at https://maven.apache.org/docs/history.html. System Requirements ------------------- JDK: 1.7 or above (this is to execute Maven - it still allows you to build against 1.3 and prior JDK's). Memory: No minimum requirement. Disk: Approximately 10MB is required for the Maven installation itself. In addition to that, additional disk space will be used for your local Maven repository. The size of your local repository will vary depending on usage but expect at least 500MB. Operating System: Windows: Windows 2000 or above. Unix based systems (Linux, Solaris and Mac OS X) and others: No minimum requirement. Installing Maven ---------------- 1) Unpack the archive where you would like to store the binaries, e.g.: Unix-based operating systems (Linux, Solaris and Mac OS X) tar zxvf apache-maven-3.x.y.tar.gz Windows unzip apache-maven-3.x.y.zip 2) A directory called "apache-maven-3.x.y" will be created. 3) Add the bin directory to your PATH, e.g.: Unix-based operating systems (Linux, Solaris and Mac OS X) export PATH=/usr/local/apache-maven-3.x.y/bin:$PATH
Windows
set PATH="c:\program files\apache-maven-3.x.y\bin";%PATH%

4) Make sure JAVA_HOME is set to the location of your JDK

5) Run "mvn --version" to verify that it is correctly installed.

Licensing
---------

Maven URLS
----------

Release Notes:      https://maven.apache.org/docs/history.html
Mailing Lists:      https://maven.apache.org/mailing-lists.html
Source Code:        https://gitbox.apache.org/repos/asf/maven.git
Issue Tracking:     https://issues.apache.org/jira/browse/MNG
Wiki:               https://cwiki.apache.org/confluence/display/MAVEN/
Available Plugins:  https://maven.apache.org/plugins/
apache-maven-3.8.7\bin\m2.conf
main is org.apache.maven.cli.MavenCli from plexus.core

set maven.conf default ${maven.home}/conf [plexus.core] load${maven.conf}/logging
optionally ${maven.home}/lib/ext/*.jar load${maven.home}/lib/*.jar
apache-maven-3.8.7\bin\mvn

apache-maven-3.8.7\bin\mvn.cmd
@REM Licensed to the Apache Software Foundation (ASF) under one
@REM or more contributor license agreements.  See the NOTICE file
@REM distributed with this work for additional information
@REM to you under the Apache License, Version 2.0 (the
@REM "License"); you may not use this file except in compliance
@REM with the License.  You may obtain a copy of the License at
@REM
@REM
@REM Unless required by applicable law or agreed to in writing,
@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
@REM KIND, either express or implied.  See the License for the
@REM specific language governing permissions and limitations

@REM -----------------------------------------------------------------------------
@REM Apache Maven Startup Script
@REM
@REM Environment Variable Prerequisites
@REM
@REM   JAVA_HOME          Must point at your Java Development Kit installation.
@REM   MAVEN_BATCH_ECHO  (Optional) Set to 'on' to enable the echoing of the batch commands.
@REM   MAVEN_BATCH_PAUSE (Optional) set to 'on' to wait for a key stroke before ending.
@REM   MAVEN_OPTS        (Optional) Java runtime options used when Maven is executed.
@REM -----------------------------------------------------------------------------

@REM Begin all REM lines with '@' in case MAVEN_BATCH_ECHO is 'on'
@echo off
@REM enable echoing my setting MAVEN_BATCH_ECHO to 'on'
@if "%MAVEN_BATCH_ECHO%"=="on" echo %MAVEN_BATCH_ECHO%

@REM Execute a user defined script before this one
if not "%MAVEN_SKIP_RC%"=="" goto skipRcPre
@REM check for pre script, once with legacy .bat ending and once with .cmd ending
if exist "%USERPROFILE%\mavenrc_pre.bat" call "%USERPROFILE%\mavenrc_pre.bat" %*
if exist "%USERPROFILE%\mavenrc_pre.cmd" call "%USERPROFILE%\mavenrc_pre.cmd" %*
:skipRcPre

@setlocal

set ERROR_CODE=0

@REM ==== START VALIDATION ====
if not "%JAVA_HOME%"=="" goto OkJHome
for %%i in (java.exe) do set "JAVACMD=%%~$PATH:i" goto checkJCmd :OkJHome set "JAVACMD=%JAVA_HOME%\bin\java.exe" :checkJCmd if exist "%JAVACMD%" goto chkMHome echo The JAVA_HOME environment variable is not defined correctly, >&2 echo this environment variable is needed to run this program. >&2 goto error :chkMHome set "MAVEN_HOME=%~dp0" set "MAVEN_HOME=%MAVEN_HOME:~0,-5%" if not "%MAVEN_HOME%"=="" goto checkMCmd goto error :checkMCmd if exist "%MAVEN_HOME%\bin\mvn.cmd" goto init goto error @REM ==== END VALIDATION ==== :init set MAVEN_CMD_LINE_ARGS=%* @REM Find the project basedir, i.e., the directory that contains the directory ".mvn". @REM Fallback to current working directory if not found. set "MAVEN_PROJECTBASEDIR=%MAVEN_BASEDIR%" if not "%MAVEN_PROJECTBASEDIR%"=="" goto endDetectBaseDir set "EXEC_DIR=%CD%" set "WDIR=%EXEC_DIR%" @REM Look for the --file switch and start the search for the .mvn directory from the specified @REM POM location, if supplied. set FILE_ARG= :arg_loop if "%~1" == "-f" ( set "FILE_ARG=%~2" shift goto process_file_arg ) if "%~1" == "--file" ( set "FILE_ARG=%~2" shift goto process_file_arg ) @REM If none of the above, skip the argument shift if not "%~1" == "" ( goto arg_loop ) else ( goto findBaseDir ) :process_file_arg if "%FILE_ARG%" == "" ( goto findBaseDir ) if not exist "%FILE_ARG%" ( echo POM file "%FILE_ARG%" specified the -f/--file command-line argument does not exist >&2 goto error ) if exist "%FILE_ARG%\*" ( set "POM_DIR=%FILE_ARG%" ) else ( call :get_directory_from_file "%FILE_ARG%" ) if not exist "%POM_DIR%" ( echo Directory "%POM_DIR%" extracted from the -f/--file command-line argument "%FILE_ARG%" does not exist >&2 goto error ) set "WDIR=%POM_DIR%" goto findBaseDir :get_directory_from_file set "POM_DIR=%~dp1" :stripPomDir if not "_%POM_DIR:~-1%"=="_\" goto pomDirStripped set "POM_DIR=%POM_DIR:~0,-1%" goto stripPomDir :pomDirStripped exit /b :findBaseDir cd /d "%WDIR%" set "WDIR=%CD%" :findBaseDirLoop if exist ".mvn" goto baseDirFound cd .. IF "%WDIR%"=="%CD%" goto baseDirNotFound set "WDIR=%CD%" goto findBaseDirLoop :baseDirFound set "MAVEN_PROJECTBASEDIR=%WDIR%" cd /d "%EXEC_DIR%" goto endDetectBaseDir :baseDirNotFound if "_%EXEC_DIR:~-1%"=="_\" set "EXEC_DIR=%EXEC_DIR:~0,-1%" set "MAVEN_PROJECTBASEDIR=%EXEC_DIR%" cd /d "%EXEC_DIR%" :endDetectBaseDir set "jvmConfig=\.mvn\jvm.config" if not exist "%MAVEN_PROJECTBASEDIR%%jvmConfig%" goto endReadAdditionalConfig @setlocal EnableExtensions EnableDelayedExpansion for /F "usebackq delims=" %%a in ("%MAVEN_PROJECTBASEDIR%\.mvn\jvm.config") do set JVM_CONFIG_MAVEN_PROPS=!JVM_CONFIG_MAVEN_PROPS! %%a @endlocal & set JVM_CONFIG_MAVEN_PROPS=%JVM_CONFIG_MAVEN_PROPS% :endReadAdditionalConfig for %%i in ("%MAVEN_HOME%"\boot\plexus-classworlds-*) do set CLASSWORLDS_JAR="%%i" set CLASSWORLDS_LAUNCHER=org.codehaus.plexus.classworlds.launcher.Launcher "%JAVACMD%" ^ %JVM_CONFIG_MAVEN_PROPS% ^ %MAVEN_OPTS% ^ %MAVEN_DEBUG_OPTS% ^ -classpath %CLASSWORLDS_JAR% ^ "-Dclassworlds.conf=%MAVEN_HOME%\bin\m2.conf" ^ "-Dmaven.home=%MAVEN_HOME%" ^ "-Dlibrary.jansi.path=%MAVEN_HOME%\lib\jansi-native" ^ "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" ^ %CLASSWORLDS_LAUNCHER% %MAVEN_CMD_LINE_ARGS% if ERRORLEVEL 1 goto error goto end :error set ERROR_CODE=1 :end @endlocal & set ERROR_CODE=%ERROR_CODE% if not "%MAVEN_SKIP_RC%"=="" goto skipRcPost @REM check for post script, once with legacy .bat ending and once with .cmd ending if exist "%USERPROFILE%\mavenrc_post.bat" call "%USERPROFILE%\mavenrc_post.bat" if exist "%USERPROFILE%\mavenrc_post.cmd" call "%USERPROFILE%\mavenrc_post.cmd" :skipRcPost @REM pause the script if MAVEN_BATCH_PAUSE is set to 'on' if "%MAVEN_BATCH_PAUSE%"=="on" pause if "%MAVEN_TERMINATE_CMD%"=="on" exit %ERROR_CODE% cmd /C exit /B %ERROR_CODE% apache-maven-3.8.7\bin\mvnDebug apache-maven-3.8.7\bin\mvnDebug.cmd @REM Licensed to the Apache Software Foundation (ASF) under one @REM or more contributor license agreements. See the NOTICE file @REM distributed with this work for additional information @REM regarding copyright ownership. The ASF licenses this file @REM to you under the Apache License, Version 2.0 (the @REM "License"); you may not use this file except in compliance @REM with the License. You may obtain a copy of the License at @REM @REM http://www.apache.org/licenses/LICENSE-2.0 @REM @REM Unless required by applicable law or agreed to in writing, @REM software distributed under the License is distributed on an @REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @REM KIND, either express or implied. See the License for the @REM specific language governing permissions and limitations @REM under the License. @REM ----------------------------------------------------------------------------- @REM Apache Maven Debug Script @REM @REM Environment Variable Prerequisites @REM @REM JAVA_HOME Must point at your Java Development Kit installation. @REM MAVEN_BATCH_ECHO (Optional) Set to 'on' to enable the echoing of the batch commands. @REM MAVEN_BATCH_PAUSE (Optional) set to 'on' to wait for a key stroke before ending. @REM MAVEN_OPTS (Optional) Java runtime options used when Maven is executed. @REM MAVEN_SKIP_RC (Optional) Flag to disable loading of mavenrc files. @REM MAVEN_DEBUG_ADDRESS (Optional) Set the debug address. Default value is 8000 @REM ----------------------------------------------------------------------------- @REM Begin all REM lines with '@' in case MAVEN_BATCH_ECHO is 'on' @echo off @REM set title of command window title %0 @REM enable echoing by setting MAVEN_BATCH_ECHO to 'on' @if "%MAVEN_BATCH_ECHO%"=="on" echo %MAVEN_BATCH_ECHO% @setlocal IF "%MAVEN_DEBUG_ADDRESS%"=="" @set MAVEN_DEBUG_ADDRESS=8000 @set MAVEN_DEBUG_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=%MAVEN_DEBUG_ADDRESS% @call "%~dp0"mvn.cmd %* apache-maven-3.8.7\bin\mvnyjp apache-maven-3.8.7\boot\plexus-classworlds-2.6.0.jar apache-maven-3.8.7\boot\plexus-classworlds.license apache-maven-3.8.7\conf\settings.xml <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- | This is the configuration file for Maven. It can be specified at two levels: | | 1. User Level. This settings.xml file provides configuration for a single user, | and is normally provided in${user.home}/.m2/settings.xml.
|
|                 NOTE: This location can be overridden with the CLI option:
|
|                 -s /path/to/user/settings.xml
|
|  2. Global Level. This settings.xml file provides configuration for all Maven
|                 users on a machine (assuming they're all using the same Maven
|                 installation). It's normally provided in
|                 ${maven.conf}/settings.xml. | | NOTE: This location can be overridden with the CLI option: | | -gs /path/to/global/settings.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. Where appropriate, the default | values (values used when the setting is not specified) are provided. | |--> <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd"> <!-- localRepository | The path to the local repository maven will use to store artifacts. | | Default:${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->

<!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If set to false,
| maven will use a sensible default value, perhaps based on some other setting, for
| the parameter in question.
|
| Default: true
<interactiveMode>true</interactiveMode>
-->

<!-- offline
| Determines whether maven should attempt to connect to the network when executing a build.
| This will have an effect on artifact downloads, artifact deployment, and others.
|
| Default: false
<offline>false</offline>
-->

<!-- pluginGroups
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
|-->
<pluginGroups>
<!-- pluginGroup
| Specifies a further group identifier to use for plugin lookup.
<pluginGroup>com.your.plugins</pluginGroup>
-->
</pluginGroups>

<!-- proxies
| This is a list of proxies which can be used on this machine to connect to the network.
| Unless otherwise specified (by system property or command-line switch), the first proxy
| specification in this list marked as active will be used.
|-->
<proxies>
<!-- proxy
| Specification for one proxy, to be used in connecting to the network.
|
<proxy>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<host>proxy.host.net</host>
<port>80</port>
<nonProxyHosts>local.net|some.host.com</nonProxyHosts>
</proxy>
-->
</proxies>

<!-- servers
| This is a list of authentication profiles, keyed by the server-id used within the system.
| Authentication profiles can be used whenever maven must make a connection to a remote server.
|-->
<servers>
<!-- server
| Specifies the authentication information to use when connecting to a particular server, identified by
| a unique name within the system (referred to by the 'id' attribute below).
|
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
|       used together.
|
<server>
<id>deploymentRepo</id>
</server>
-->

<!-- Another sample, using keys to authenticate.
<server>
<id>siteServer</id>
<privateKey>/path/to/private/key</privateKey>
<passphrase>optional; leave empty if not used.</passphrase>
</server>
-->
</servers>

<!-- mirrors
|
| It works like this: a POM may declare a repository to use in resolving certain artifacts.
| However, this repository may have problems with heavy traffic at times, so people have mirrored
| it to several places.
|
| That repository definition will have a unique id, so we can create a mirror reference for that
| repository, to be used as an alternate download site. The mirror site will be the preferred
| server for that repository.
|-->
<mirrors>
<!-- mirror
| Specifies a repository mirror site to use instead of a given repository. The repository that
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
|
<mirror>
<id>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://my.repository.com/repo/path</url>
</mirror>
-->
<mirror>
<id>maven-default-http-blocker</id>
<mirrorOf>external:http:*</mirrorOf>
<name>Pseudo repository to mirror external repositories initially using HTTP.</name>
<url>http://0.0.0.0/</url>
<blocked>true</blocked>
</mirror>
</mirrors>

<!-- profiles
| This is a list of profiles which can be activated in a variety of ways, and which can modify
| the build process. Profiles provided in the settings.xml are intended to provide local machine-
| specific paths and repository locations which allow the build to work in the local environment.
|
| For example, if you have an integration testing plugin - like cactus - that needs to know where
| your Tomcat instance is installed, you can provide a variable here such that the variable is
| dereferenced during the build process to configure the cactus plugin.
|
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
| section of this document (settings.xml) - will be discussed later. Another way essentially
| relies on the detection of a system property, either matching a particular value for the property,
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
| Finally, the list of active profiles can be specified directly from the command line.
|
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
|       repositories, plugin repositories, and free-form properties to be used as configuration
|       variables for plugins in the POM.
|
|-->
<profiles>
<!-- profile
| Specifies a set of introductions to the build process, to be activated using one or more of the
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
| or the command line, profiles have to have an ID that is unique.
|
| An encouraged best practice for profile identification is to use a consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| This will make it more intuitive to understand what the set of introduced profiles is attempting
| to accomplish, particularly when you only have a list of profile id's for debug.
|
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
<profile>
<id>jdk-1.4</id>

<activation>
<jdk>1.4</jdk>
</activation>

<repositories>
<repository>
<id>jdk14</id>
<name>Repository for JDK 1.4 builds</name>
<url>http://www.myhost.com/maven/jdk14</url>
<layout>default</layout>
<snapshotPolicy>always</snapshotPolicy>
</repository>
</repositories>
</profile>
-->

<!--
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| might hypothetically look like:
|
| ...
| <plugin>
|   <groupId>org.myco.myplugins</groupId>
|   <artifactId>myplugin</artifactId>
|
|   <configuration>
|     <tomcatLocation>${tomcatPath}</tomcatLocation> | </configuration> | </plugin> | ... | | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to | anything, you could just leave off the <value/> inside the activation-property. | <profile> <id>env-dev</id> <activation> <property> <name>target-env</name> <value>dev</value> </property> </activation> <properties> <tomcatPath>/path/to/tomcat/instance</tomcatPath> </properties> </profile> --> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> </settings> apache-maven-3.8.7\conf\toolchains.xml <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- | This is the toolchains file for Maven. It can be specified at two levels: | | 1. User Level. This toolchains.xml file provides configuration for a single user, | and is normally provided in${user.home}/.m2/toolchains.xml.
|
|                 NOTE: This location can be overridden with the CLI option:
|
|                 -t /path/to/user/toolchains.xml
|
|  2. Global Level. This toolchains.xml file provides configuration for all Maven
|                 users on a machine (assuming they're all using the same Maven
|                 installation). It's normally provided in
|                 ${maven.conf}/toolchains.xml. | | NOTE: This location can be overridden with the CLI option: | | -gt /path/to/global/toolchains.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. |--> <toolchains xmlns="http://maven.apache.org/TOOLCHAINS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/TOOLCHAINS/1.1.0 http://maven.apache.org/xsd/toolchains-1.1.0.xsd"> <!-- | With toolchains you can refer to installations on your system. This | way you don't have to hardcode paths in your pom.xml. | | Every toolchain consist of 3 elements: | * type: the type of tool. An often used value is 'jdk'. Toolchains-aware | plugins should document which type you must use. | | * provides: A list of key/value-pairs. | Based on the toolchain-configuration in the pom.xml Maven will search for | matching <provides/> configuration. You can decide for yourself which key-value | pairs to use. Often used keys are 'version', 'vendor' and 'arch'. By default | the version has a special meaning. If you configured in the pom.xml '1.5' | Maven will search for 1.5 and above. | | * configuration: Additional configuration for this tool. | Look for documentation of the toolchains-aware plugin which configuration elements | can be used. | | See also https://maven.apache.org/guides/mini/guide-using-toolchains.html | | General example <toolchain> <type/> <provides> <version>1.0</version> </provides> <configuration/> </toolchain> | JDK examples <toolchain> <type>jdk</type> <provides> <version>1.5</version> <vendor>sun</vendor> </provides> <configuration> <jdkHome>/path/to/jdk/1.5</jdkHome> </configuration> </toolchain> <toolchain> <type>jdk</type> <provides> <version>1.6</version> <vendor>sun</vendor> </provides> <configuration> <jdkHome>/path/to/jdk/1.6</jdkHome> </configuration> </toolchain> --> </toolchains> apache-maven-3.8.7\conf\logging\simplelogger.properties apache-maven-3.8.7\lib\commons-cli-1.4.jar apache-maven-3.8.7\lib\commons-cli.license apache-maven-3.8.7\lib\commons-lang3-3.8.1.jar apache-maven-3.8.7\lib\commons-lang3.license apache-maven-3.8.7\lib\guava-25.1-android.jar apache-maven-3.8.7\lib\guava.license apache-maven-3.8.7\lib\guice-4.2.2-no_aop.jar apache-maven-3.8.7\lib\guice.license apache-maven-3.8.7\lib\jansi-2.4.0.jar apache-maven-3.8.7\lib\jansi.license apache-maven-3.8.7\lib\javax.annotation-api-1.2.jar apache-maven-3.8.7\lib\javax.annotation-api.license apache-maven-3.8.7\lib\javax.inject-1.jar apache-maven-3.8.7\lib\javax.inject.license apache-maven-3.8.7\lib\jcl-over-slf4j-1.7.36.jar apache-maven-3.8.7\lib\jcl-over-slf4j.license apache-maven-3.8.7\lib\maven-artifact-3.8.7.jar apache-maven-3.8.7\lib\maven-builder-support-3.8.7.jar apache-maven-3.8.7\lib\maven-compat-3.8.7.jar apache-maven-3.8.7\lib\maven-core-3.8.7.jar apache-maven-3.8.7\lib\maven-embedder-3.8.7.jar apache-maven-3.8.7\lib\maven-model-3.8.7.jar apache-maven-3.8.7\lib\maven-model-builder-3.8.7.jar apache-maven-3.8.7\lib\maven-plugin-api-3.8.7.jar apache-maven-3.8.7\lib\maven-repository-metadata-3.8.7.jar apache-maven-3.8.7\lib\maven-resolver-api-1.6.3.jar apache-maven-3.8.7\lib\maven-resolver-connector-basic-1.6.3.jar apache-maven-3.8.7\lib\maven-resolver-impl-1.6.3.jar apache-maven-3.8.7\lib\maven-resolver-provider-3.8.7.jar apache-maven-3.8.7\lib\maven-resolver-spi-1.6.3.jar apache-maven-3.8.7\lib\maven-resolver-transport-wagon-1.6.3.jar apache-maven-3.8.7\lib\maven-resolver-util-1.6.3.jar apache-maven-3.8.7\lib\maven-settings-3.8.7.jar apache-maven-3.8.7\lib\maven-settings-builder-3.8.7.jar apache-maven-3.8.7\lib\maven-shared-utils-3.3.4.jar apache-maven-3.8.7\lib\maven-slf4j-provider-3.8.7.jar apache-maven-3.8.7\lib\org.eclipse.sisu.inject-0.3.5.jar apache-maven-3.8.7\lib\org.eclipse.sisu.inject.license apache-maven-3.8.7\lib\org.eclipse.sisu.plexus-0.3.5.jar apache-maven-3.8.7\lib\org.eclipse.sisu.plexus.license apache-maven-3.8.7\lib\plexus-cipher-2.0.jar apache-maven-3.8.7\lib\plexus-cipher.license apache-maven-3.8.7\lib\plexus-component-annotations-2.1.0.jar apache-maven-3.8.7\lib\plexus-component-annotations.license apache-maven-3.8.7\lib\plexus-interpolation-1.26.jar apache-maven-3.8.7\lib\plexus-interpolation.license apache-maven-3.8.7\lib\plexus-sec-dispatcher-2.0.jar apache-maven-3.8.7\lib\plexus-sec-dispatcher.license apache-maven-3.8.7\lib\plexus-utils-3.3.1.jar apache-maven-3.8.7\lib\plexus-utils.license apache-maven-3.8.7\lib\slf4j-api-1.7.36.jar apache-maven-3.8.7\lib\slf4j-api.license apache-maven-3.8.7\lib\wagon-file-3.5.3.jar apache-maven-3.8.7\lib\wagon-http-3.5.3-shaded.jar apache-maven-3.8.7\lib\wagon-provider-api-3.5.3.jar apache-maven-3.8.7\lib\ext\README.txt Use this directory to contribute 3rd-party extensions to the Maven core. These extensions can either extend or override Maven's default implementation. apache-maven-3.8.7\lib\jansi-native\README.txt This directory contains Jansi native libraries extracted from Jansi JAR. You can add your own build for platforms not natively supported by Jansi. See here [1] on how to compile for your platform and and here [2] how libraries follow Jansi's directory and filename conventions. [1] https://github.com/fusesource/jansi/tree/master/src/main/native [2] https://github.com/fusesource/jansi/blob/321a8ff71c731e10f4ea05c607860180276b2215/src/main/java/org/fusesource/jansi/internal/OSInfo.java apache-maven-3.8.7\lib\jansi-native\Windows\x86\jansi.dll md5: 0E396DB1F1371448BE55AD0B1542DC0B | sha1: 492BD09333E536E51D17CAFFCF6B7B56C4AFCDBF | sha256: 1D6314DA4B3A7A5E9DDED6B0CC1B83F15F8F603897AE00CFE98EF171285620F3 | sha512: 4EEE14C446A19128D4E049965DB8D095EA1AFF74BE10E9790BEA50A94EAF294CD3A705A19BDD5D649D944404562D66C7A7E422A5B4512EAD24785755AEB7A2FB apache-maven-3.8.7\lib\jansi-native\Windows\x86_64\jansi.dll md5: A7A3EFD305C910CD0850F24F17ACEC86 | sha1: 6303F154EDEAA18A7AEB3997E9EF3634E5EE1171 | sha256: D23FC9293B68781D43314403048D6DC655FA4620B6B4DB3DCD345C52C332A2F4 | sha512: 1308C0CCD57117E27BFCEF106B96448A5E1D2A47D734D4D79602A6608813EF0482396AE35DE0A5F2B22EC7DB2162B59A7A39490DFF16B9E700A17A813C59E564 legal\LICENSE.txt From: https://maven.apache.org/ref/3.0/license.html ------- Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. legal\VERIFICATION.txt VERIFICATION Verification is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy. 1. Download the maven binary zip at x32: https://downloads.apache.org/maven/maven-3/3.8.7/binaries/apache-maven-3.8.7-bin.zip 2. Extract the maven zip 3. Compare the checksums of the files included in the maven zip with the checksums of the files in the maven directory in the nupkg. A PowerShell (v4+) function to automate this comparison is below. It should return nothing if the directories have identical files, and return the difference if they are different. Function Compare-Directories { param( [string]$nuspecDir,
[string]$checkDir )$nuspecDirHash = Get-ChildItem -Recurse -File -Path $nuspecDir | Get-FileHash -Algorithm SHA256$checkDirHash = Get-ChildItem -Recurse -File -Path $checkDir | Get-FileHash -Algorithm SHA256 Compare-Object -ReferenceObject$nuspecDirHash -DifferenceObject $checkDirHash -Property hash -PassThru } Compare-Directories -nuspecDir \path\to\extracted\nupkg\maven-directory -checkDir \path\to\extracted\maven\archive\ tools\chocolateybeforemodify.ps1$ErrorActionPreference = 'Stop'
$toolsDir = Split-Path$MyInvocation.MyCommand.Definition
$installFolders = Split-Path$toolsDir
. $toolsDir\helpers.ps1 # Delete any folders from older versions before upgrading or uninstalling Remove-PreviousVersions -installFolders$installFolders
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'$version = '3.8.7'
$name = "apache-maven-$version"
$toolsDir = Split-Path$MyInvocation.MyCommand.Definition
$installLocation = Join-Path (Split-Path$toolsDir) $name$pathToAdd = Join-Path $installLocation 'bin'$m2_repo = Join-Path $env:USERPROFILE '.m2' .$toolsDir\helpers.ps1

New-Item -Path $m2_repo -Type directory -Force # Clean Old Environment variables Uninstall-OldM2PathFromRegistry Uninstall-ChocolateyEnvironmentVariable -VariableName 'M2_HOME' -VariableType Machine # Adding to path instead of shimming; see comment: https://chocolatey.org/packages/maven#comment-4454809638 Install-ChocolateyPath -PathToInstall$pathToAdd -PathType 'Machine'

if (!(Get-Command javac.exe -ea 0)) {
Show-JDKWarning
}

$env:ChocolateyPackageInstallLocation =$installLocation
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'$toolsDir = Split-Path $MyInvocation.MyCommand.Definition$installFolders = Split-Path $toolsDir .$toolsDir\helpers.ps1

# Clean Old Environment variables
Uninstall-OldM2PathFromRegistry
Uninstall-ChocolateyEnvironmentVariable -VariableName 'M2_HOME' -VariableType Machine

# Delete any folders from older versions before upgrading or uninstalling
Remove-PreviousVersions -installFolders $installFolders tools\helpers.ps1 Function Uninstall-PathFromRegistry($pathToRemove) {
# Using registry method prevents expansion (and loss) of environment variables (whether the target of the removal or not)
# To avoid bad situations - does not use substring matching or regular expressions
# Removes duplicates of the target removal path, Cleans up double ";", Handles ending "\"
try {
$regKey = [Microsoft.Win32.Registry]::LocalMachine.OpenSubKey('SYSTEM\CurrentControlSet\Control\Session Manager\Environment',$true)
$unexpandedPath =$regKey.GetValue('Path', $null, 'DoNotExpandEnvironmentNames') foreach ($path in "$unexpandedPath".split(';')) { if ($pathToRemove -ine $path -and "$pathToRemove\" -ine $path) { [string[]]$newpath += "$path" } }$assembledNewPath = ($newpath -join (';')).trimend(';')$regKey.SetValue("Path", $assembledNewPath, "ExpandString") } finally {$regKey.Dispose()
}
}

Function Uninstall-OldM2PathFromRegistry() {
$pathToRemove = Join-Path '%M2_HOME%' 'bin' Uninstall-PathFromRegistry -pathToRemove$pathToRemove
}

Function Remove-PreviousVersions($installFolders) {$installs = Get-Childitem -Path $installFolders -Filter "apache-maven-*"$installs | ForEach-Object {
Write-host "Removing old version $($_.name)"
Uninstall-PathFromRegistry -pathToRemove (Join-Path $_.fullname 'bin') Remove-Item$_.fullname -Force -Recurse
}
}

Function Show-JDKWarning () {
Write-Output "**********************************************************************************"
Write-Output "*                       !! No Java JDK detected on path !!                       *"
Write-Output "*               Maven requires that a JDK be installed to function               *"
Write-Output "*                                                                                *"
Write-Output "*      However, this package does not take a dependency on any one specific      *"
Write-Output "*          JDK package so as to not lock you into any specific JDK build         *"
Write-Output "*                                                                                *"
Write-Output "*See this issue on progress for the 'provides' nuspec element that will fix this:*"
Write-Output "*                 https://github.com/chocolatey/choco/issues/858                 *"
Write-Output "**********************************************************************************"
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Maven 3.8.6 84236 Saturday, June 11, 2022 Approved
Maven 3.8.5 39346 Sunday, March 13, 2022 Approved
Maven 3.8.4 50149 Saturday, November 20, 2021 Approved
Maven 3.8.3.20211022 12823 Friday, October 22, 2021 Approved
Maven 3.8.3 9382 Monday, October 4, 2021 Approved
Maven 3.8.2 29662 Saturday, August 14, 2021 Approved
Maven 3.8.1 47657 Saturday, April 10, 2021 Approved
Maven 3.6.3.20220128 74 Friday, January 28, 2022 Approved

This package has no dependencies.

Discussion for the Maven Package