This is most probably "just" about broken Throwable implementations.
Some override getCause but does not perform checks to what it was inited
as "this" means "not yet inited" actually.
Backport of 36db1e35ca
---
https://issues.apache.org/jira/browse/MNG-7846
Checks the paths before relativizing them.
Normalize and relative before adding to result
Rename local vars
Apply to ExecutionEventLogger
---
https://issues.apache.org/jira/browse/MNG-7795
Reuse as much as possible from master, but keep existing stuff like multiModuleProjectDirectory alone.
Changes:
* interpolate user properties and arguments
* introduce session.topDirectory and session.rootDirectory expressions (for interpolation only)
* Maven fails to start if any of the new properties are undefined but their use is attempted
* leave everything else untouched
---
https://issues.apache.org/jira/browse/MNG-7774
As with previous PR (simple removal) the `-llr` got
interpreted as `-l lr`, it logged all output to `lr`
file. This would maean that use of `-llr` would still
sneakily 'work' and probably cause surprise down the
road to users.
Returned the option, and expicitly checking for it's
presence to be able to fail with meaningful message.
---
https://issues.apache.org/jira/browse/MNG-7713
There is really no need for it, and there is a resolver
option if really must (but really should not, local repo
is and should be considered as transient).
---
https://issues.apache.org/jira/browse/MNG-7713
Since we don't have a clear specification of the file format change
reading of the file to a one-arg-per-line basis just like Java's
@argfiles or Python's argparse would handle it.
Consider that jvm.config suffers from the same issue its parsing is not
portable between Bourne shell and Windows Command prompt.
This adds support for property interpolation in extensions.xml to allow
advanced use cases where one wants to contribute certain things via the
commandline.
This closes#673
The MavenCliTest.testStyleColors is not failing when the build
is under JDK 8 or JDK 11.
After changing to JDK 16, the test fails, this commit is to fix
the NullPointerException.
Tested on JDK 8, 11 adn 16 with:
`mvn clean verify`
o MavenCli.resolveFile and
configuration.SettingsXmlConfigurationProcessor.resolveFile
utility methods are identical. Moving them into separate
ResolveFile class.
Switch from OptionBuilder to Option.Builder. Confirm by
inspection that the resulting Option objects are the same.
For now, leave GnuParser. Despite the upgrade advice in the GnuParser
Javadoc ("since 1.3, use the DefaultParser instead"), it behaves
differently.
Closes#247
Hervé Boutemy
Tamas Cservenak
Andreas Dangel
Guillaume Nodet
Andrey Bruykhov
Michael Osipov
Slawomir Jaranowski
Josef Cacek
Karl Heinz Marbaise
Christoph Läubrich
Artem Krosheninnikov
huangkaifeng
Rostislav Krasny
Carlos Chacin
Sylwester Lachiewicz
Anatoly Zaretsky
Joseph Walton
rfscholte
Raymond Auge
Guy Brand
HoaPhan
Christian Schulte