gnodet commented on PR #14:
URL:
https://github.com/apache/maven-toolchains-plugin/pull/14#issuecomment-1963004701
> > Cant we make toolchain.xml physically optional and replaced by some env
var naming convention instead? This way these new mojos are not needed and
therefore no need to maintain the generated value which is a challenge to
maintain until you make toolchain.xml an useless indirection using vars from my
XP. Sounds more natural to integrate with specific setups and CI and requires
less effort for us IMHO.
>
> Wouldn't it be great if `settings.xml` could also be made optional by
usage of env vars as well?
Settings are already interpolated so we can use env vars already, I'm using
it locally with the following:
```
<mirror>
<id>central</id>
<mirrorOf>central</mirrorOf>
<url>${env.MAVEN_CENTRAL}</url>
</mirror>
```
so that I can point to a mirror on my LAN when available.
Toolchains are also interpolated and env vars seems to be supported too fwiw.
--
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
