What's new in XMvn 0.5.0
* Major features
* XMvn Subst
Version 0.5.0 brings a new tool - XMvn Subst. This tool is able
to replace individual artifact files with symbolic links to
corresponding files in system artifact repository. It is also
able to recursively process whole directories.
* XMvn Bisect
Since version 0.5.0 a new tool - XMvn Bisect - is available.
This tool helps automating debugging build failures using
bisection method. It first builds project using dependencies
coming from system repository only, next only from remote
repositories, then halves dependency set recursively until it
finds differences which are causing build failure.
* Minor features
* Basic support for dependency version ranges
In previous versions XMvn did not support dependency version
ranges. If range was used in POM then Maven would try to
resolve all available versions from remote repository and pick
the best match.
Starting from XMvn 0.5.0 any dependency version ranges without
recommended version specified are replaced with version
<<<SYSTEM>>>, which means default artifact version in the
system. This prevents Maven from trying to use remote
* Improved configuration loading
Starting from version 0.5.0 configuration is read only once at
the beginning of the build. In previous versions configuration
was read every time it was needed. The new approach is not only
faster, but also allows configuration to be modified by plugins
* Better handling of inaccurate configuration
In previous versions any packaging rules that didn't match any
artifact in the reactor were silently ignored. Since version
0.5.0 any non-optional packaging rule that is not used causes
the build to fail.
* Minor bugfixes
* Incorrect path to JPP artifacts
Paths to JPP artifacts containing more than one slash in groupId
were generated incorrectly. This could cause dependency
resolution failures in some rare cases. This bug was fixed in
* Fixed exit code of XMvn Resolve
Now <<<xmvn-resolve>>> returns 0 when it successfully resolves
all artifacts, 1 on failure to resolve one or more artifacts and
2 when some other error occurs. In the last case a stack trace
is printed too.
* Fixed installation of artifact marked as not installable
Before version 0.5.0 XMvn tried to find installers for all
artifacts in the reactor, even for those marked as not
installable. As a result reactors that contained artifacts with
unsupported packaging types failed to build, even if instalation
of these artifacts was explicitly skipped.
This bug was fixed in XMvn 0.5.0, in which artifact packaging
type has to be supported only if the artifact is installable.