Apache Maven 3.8.2

What's new in this version:

Sub-task:
- ArrayIndexOutOfBoundsException caused by pom.xml with invalid/duplicate XML

Fixed::
- Multithreaded building can create bad files for downloaded artifacts in local repository
- NPE during resolution of dependencies - parallel mode
- Artifact resolution sporadically fails in parallel builds
- Maven on No-File-Lock Systems
- Adding serval times the same artifact via MavenProjectHelper (attachArtifact) keep adding to the List duplicate artifacts
- GetResource ('/) returns 'null' if build is started with -f
- ArrayIndexOutOfBoundsException when parsing POM
- Jansi messes up System.err and System.out
- Option -Dstyle.color=always doesn't force color output
- Intermittent failures while downloading GAVs from Nexus
- 'mavenrc_pre' script does not receive arguments like mavenrc in Bourne shell does
- mvn color output escape keys w/ "| tee xxx.log" on Win with git/bash
- StackOverflowError when version ranges are unsolvable and graph contains a cycle
- Plugin with ${project.groupId} resolved improperly
- NullPointerException for DefaultArtifactDescriptorReader.loadPom
- DependencyResolutionException breaks serialization
- ProjectBuilderTest uses Guava, but Guava is not defined in dependencies
- Parallel build fails due to missing JAR artifacts in compilePath
- Prevent printing the EXEC_DIR when it's just a disk letter
- Maven compile with properties ${artifactId} and ${project.build.finalName} occurs java.lang.NullPointerException
- StringSearchModelInterpolatorTest fails on symlinked paths
- Maven version sorting is internally inconsistent
- Plugin key can get out of sync with artifactId and groupId
- metadata.mdo contains invalid link to schema
- Option -B still showing formatting when used with --version
- StackOverflowError thrown if a cycle exists in BOM imports
- mvnDebug does not work on Java 11+
- NullPointerException in MavenCliTest.testStyleColors in JDK 16
- make sources jar reproducible (upgrade maven-source-plugin to 3.2.1)
- Error thrown during uninstalling of JAnsi
New Feature:
- Introduce MAVEN_DEBUG_ADDRESS in mvnDebug scripts

Improvement:
- Concurrent-safe access to local Maven repository
- Parallel builder should use the module name as thread name
- Set the same timestamp in multi module builds
- Remove profiles in maven-model
- Remove unnecessary filtering configuration
- Prefer System.lineSeparator() over system properties
- Replace deprecated StringUtils#defaultString() from Plexus Utils
- Simplify detection of the MAVEN_HOME and make it fully qualified on Windows
- Use StandardCharsets and remove outdated @SuppressWarnings
- Don't box primitives where it's not needed
- Build not easily reproducible when built from source release archive
- Inconsistent library versions notice
- Improve the command line output from maven-artifact
- Reorder groupId before artifactId when writing an exclusion using maven-model
- Omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the problem
- Use HTTPS for schema location in global settings.xml
- Add a --color option
- Allow to associate pomFile/${basedir} with DefaultProjectBuilder.build(ModelSource, ...)
- Make --color option behave more like BSD/GNU grep's --color option
- Make --version support -q
- Describe explicit and recommended version for VersionRange.createFromVersionSpec()
- Load mavenrc from /usr/local/etc also in Bourne shell script

Task:
- Maven 3.6.0 and Surefire problem
- Cleanup POM File after version upgrade
- Remove expansion of Jansi native libraries
- document .mavenrc/maven_pre.bat|cmd scripts and MAVEN_SKIP_RC environment variable

Dependency upgrade:
- Found CVEs in your dependencies - plexus-utils (tests)
- Upgrade Maven Parent to 34
- Upgrade plexus-cipher 1.8
- Upgrade SLF4J to 1.7.30
- Upgrade Maven Resolver to 1.6.3
- Upgrade Maven Shared Utils to 3.3.4
- Upgrade Jansi to 2.3.3
- Upgrade Guice to 4.2.2
- Upgrade Jansi to 2.3.4
- Upgrade SLF4J to 1.7.32