As title says, XSD is ancient old 2.0.0, while all
latest assembly plugins uses 2.1.0.
Not that this matters or changes anything at all,
this is more about correctness.
Addendum to be2b7f890d98af20eb0753650b6605a68a97ac05:
* fix property name to align with existing ones
* fix logging configuration as no more shaded httpClient
* fix constant names
But keep Wagon as default transport. This PR merely includes
resolver http and file transport and switches wagon-http
to non-shaded one.
Changes:
* switch to non-shaded wagon-http (as httpClient is now shared)
* include resolver http and file transport
* override resolver default behaviour (native transport preferred over wagon, when both on classpath)
* provide simplistic means to choose transport
The chosen transport can be seen in debug (-X) output on line
`[DEBUG] Using transporter XXX...`
The `-Dmaven.transport` simplistic switch can be used to choose transport:
* not set: default, that is Wagon
* `wagon`: explicitly sets Wagon
* `resolver`: explicitly sets resolver native transports (file and http)
* `auto`: relies on resolver "auto discovery" (priorities, etc). This is MUST to keep transport pluggable with 3rd party transports. In fact, this was the default so far in Maven, along with the fact that native resolver transports were not included (as resolver prefers native ones over Wagon).
In some circumstances the init script calls `which`, which may or may not be
available on the host system. Instead, use `command -v`, which is nearly
equivalent. One area it differs is if the command being queried is defined as
a shell alias. To avoid that, call `unset -f command` to avoid the situation
where "command" has been re-defined as a shell function.
See here for more information on this approach:
<https://pubs.opengroup.org/onlinepubs/009695399/utilities/command.html>
Tested with bash, sh (bash invoked as sh), posh, dash, zsh and mksh.
This closes#556
Since we have replaced the old JSR 250 library with javax.annotation library we
go straight to 1.3.2 because Maven Resolver 1.7.0 introduced this already as a
transitive dependency in fc806a25eb.
The only difference between version 1.2 and 1.3.2 is a Java upgrade from 6 to 8.
This closes#539
Dramatically simplify/rework handling by leaving setting JAVA_HOME to
the user and try to load java(1) command from it. Technically Maven itself does
not require JAVA_HOME to be set. If not set, use java(1) command from
PATH on both Windows and POSIX-like systems.
This closes#514
Guillaume Nodet
Michael Osipov
Sylwester Lachiewicz
Marc Wrobel
Rafael Chaves
Tamas Cservenak
Hervé Boutemy
Jonathan Dowland