michael-o commented on code in PR #308:
URL: https://github.com/apache/maven-site/pull/308#discussion_r913205677
##########
content/markdown/configure.md:
##########
@@ -65,26 +130,35 @@ From now on this can be done much more simpler and in a
more Maven like way. So
</extensions>
```
-Now you can simply use an extension by defining the usual maven coordinates
groupId, artifactId, version as any other artifact. Furthermore all transitive
dependencies of those extensions will automatically being downloaded from your
repository. So no need to create a shaded artifact anymore.
+### `/usr/local/etc/mavenrc` + `/etc/mavenrc` + `$HOME/.mavenrc`
-### `.mvn/maven.config` file:
+Unix-like systems only:
+Configuration files executed by the Unix launcher scripts first thing, unless
+if the environment variable `$MAVEN_SKIP_RC` is set.
-It’s really hard to define a general set of options for calling the maven
command line. Starting with Maven 3.3.1+, this can be solved by
-putting this
-options to a script but this can now simple being done by defining
`${maven.projectBasedir}/.mvn/maven.config` file which contains the
-configuration options for the `mvn` command line.
+Typically environment variables - including `$PATH` - are set here.
-For example things like `-T3 -U --fail-at-end`. So you only have to call Maven
just by using `mvn
-clean package` instead of `mvn -T3 -U --fail-at-end clean package` and not to
miss the `-T3 -U --fail-at-end` options on every call. The
-`${maven.projectBasedir}/.mvn/maven.config` is located in the
`${maven.projectBasedir}/.mvn/` directory; also works if in the root of a multi
module build.
+### `%USERPROFILE%\mavenrc_pre.bat` + `%USERPROFILE%\mavenrc_pre.cmd`
-### `.mvn/jvm.config` file:
+Windows systems only:
+Configuration files executed by the Windows launcher scripts first thing
_before_ launching the Maven JVM,
+unless if the environment variable `%MAVEN_SKIP_RC%` is set.
-Starting with Maven 3.3.1+ you can define JVM configuration via
`${maven.projectBasedir}/.mvn/jvm.config` file which means you can define the
options for your build on a per project base. This file will become part of
your project and will be checked in along with your project. So no need anymore
for `MAVEN_OPTS`, `.mavenrc` files. So for example if you put the following JVM
options into the `${maven.projectBasedir}/.mvn/jvm.config` file
+This can be used to provide secrets, like the password for a keystore:
Review Comment:
Yeah, I know that issue, but the example is just bad. I.e., we shouldn't
encourage people to expose secrets like this if it isn't necessary.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
