XMvn 4.2.0

Release version 4.2.0

XMvn 4.1.0

Release version 4.1.0

XMvn 4.0.0

Release version 4.0.0

XMvn 3.1.0

Release version 3.1.0

XMvn 3.0.0

API changes

• New Configurator API

  XMvn 3.0.0 adds Configurator API service, which exposes XMvn
  configuration as Java beans.

• New MetadataResolver API

  XMvn 3.0.0 adds new API service - MetadataResolver, which
  allows resolution of metadata for artifacts installed in the
  system.

• Service locator API

  Instances of services provided by XMvn API can now be obtained
  using service locator, without using dependency injection. This
  change obsoleted XMvn Launcher module, which was removed in XMvn
  3.0.0.

• New default compiler source setting

  Since XMvn 3.0.0 compilerSource setting has a new default
  value equal to 1.6.

Changes in binary distribution

• Launcher scripts removed from binary tarball

  Launcher scripts for tools, such as xmvn-resolve,
  xmvn-install etc., as well as xmvn launcher, were
  removed. From now on, tools can be ran using java -jar
  syntax and XMvn itself can be ran using standard mvn
  launcher. This is upstream change only - downstream
  distributions may continue to provide distro-specific launchers.

• Ivy connector removed from binary tarball

  Since XMvn 3.0.0, connector for Apache Ivy is no longer included
  in binary tarball.

New features

• Ignoring duplicate metadata made configurable

  XMvn versions prior to 3.0.0 would previously always ignore
  installed artifacts, which have multiple metadata, for example
  when more than one package provides the same artifact. XMvn
  3.0.0 added new option ignoreDuplicateMetadata, which can
  be used to control this behavior.
  ignoreDuplicateMetadata is true by default, but when
  set to false XMvn will resolve metadata for the first
  artifact found, ignoring others.

• POM files for Tycho projects are not installed

  Projects built with Eclipse Tycho install JAR files in private
  locations specific to Eclipse, so POM files and metadata for
  them are not installed.

• PoC implementation of Javadoc MOJO

  XMvn 3.0.0 added new MOJO, which can be used to generate API
  documentation (javadocs) as alternative to Maven Javadoc Plugin.
  Goal xmvn-mojo:javadoc works in similar way to
  javadoc:aggregate, but it has some advantages over it.
  XMvn javadoc makes javadocs more consistent between packages -
  it unifies javadoc options, doclet used, CSS styles, and so on.
  It opens possibilities for better integration with distributions
  in the future, like for example distro-specific themes, links or
  dependencies between javadoc packages. It also has much fewer
  dependencies, which means smaller builroots and faster builds.

• More accurate builddep MOJO

  Builddep MOJO, which can be used for auto-generating
  build-requires, was rewritten almost from scratch. Now its
  output should be much more accurate.

• Partial compatibility with Maven 3.0

  XMvn 3.0.0 restores partial compatibility with Maven 3.0.

Bug fixes

• Ignoring runtime exceptions during bytecode analysis

  Previously XMvn Installer would terminate abnormally on bytecode
  it couldn't parse, such as newer bytecode than recognized by ASM
  library which XMvn uses. This has been fixed in XMvn 3.0.0.

• Coping with whitespaces in file names

  When installing files with whitespace in their names, XMvn
  Installer would previously generate incorrect file descriptor.
  XMvn 3.0.0 fixes this bug.

Other changes

• Release on Maven Central Repository

  Since 3.0.0 XMvn will be available in Maven Central Repository.

• Migrated from fedorahosted.org to GitHub

  Since fedorahosted.org, the service that XMvn used to be hosted
  on, was decommissioned, XMvn source repository was moved to new
  home, which is now at GitHub:
  https://github.com/fedora-java/xmvn/

XMvn 2.5.0

Major features

• XMvn Gradle plugin

  XMvn Gradle plugin was implemented in version 2.5.0. When
  applied on a project, this plugin automatically configures
  repositories in local mode, so that project dependencies can be
  resolved from system repository. It also provides
  xmvnInstall task, which can be used to install artifacts
  produced by the build with XMvn Installer.

• Custom buildroot option for XMvn Subst

  XMvn Subst now accepts a new option, --root, which
  specifies buildroot from which XMvn should resolve artifacts, in
  addition to standard locations. This option can be used for
  symlinking JARs produced during build. (Bug: 1226251)

Major bugfixes

• Builddep MOJO fixes

  Builddep MOJO was rewritten from scratch. The new code is more
  generic and supports many corner case in which the previous
  version produced incorrect results (bugs: 1217422, 1217425,
  1217462, 1217473).

Minor features

• Warning when builddep MOJO is ran with pure Maven

  XMvn builddep MOJO 2.5.0 will print a warning when it's ran
  outsides of XMvn.

• Allowing manifacs injection for invalid JAR files

  OpenJDK has a sanity check that prevents adding duplicate
  entries to ZIP streams. When trying to inject manifests to JAR
  files with duplicate entries XMvn would previously fail with
  "ZipException: duplicate entry". XMvn 2.5.0 added a workaround
  that allows manifest injection to such invalid JAR files.

Minor bugfixes

• GradleResolver crash when resolving tools.jar

  XMvn 2.5.0 fixes a bug that caused Gradle resolver crash when
  trying to resolve tools.jar artifact.

• Crash when effective POM generation failed

  XMvn 2.5.0 fixes a bug that caused crash with
  NullPointerException uppon failure to generate effective POM.

• Slashes in effective POM names are replaced with dots

  XMvn versions prior to 2.5.0 would try to create effective POM
  files with artifactID as name, even if it contain slash
  character. XMvn 2.5.0 fixes this bug.

Other changes

XMvn 2.5.0 drops support for rarely-used compatibility
configuration suffixes.

XMvn 2.4.0

Major features

• Support for Mock pm_request plugin

  XMvn 2.4.0 supports on-demand artifact installation via Mock
  pm_request plugin. When this plugin is enabled then XMvn will
  try to install any missing artifacts instead of failing.

Major bugfixes

• Java requires

  Generation of Java requires (rhbz#1086335) was fixed in this
  XMvn release.

Minor features

• Effective POM caching

  XMvn 2.4.0 fixes tries to avoid creating polluting system with
  temporary files. In particular effective POMs are cached in XDG
  cache directory.

XMvn 2.3.2

Minor bugfixes

• NullPointerException during model validation

  XMvn 2.3.2 fixes a NullPointerException regression in
  XMvnModelValidator, which occured during validation of models
  without build instructions.

XMvn 2.3.1

Major bugfixes

• Installation of multiple artifacts in one directory

  Version 2.3.1 fixes a bug that caused XMvn Install to fail when
  trying to install multiple artifacts to the same directory.

Minor features

• Optional dependencies in effective POM

  Since version 2.3.1 effective POMs generated by XMvn include
  information whether given project dependency is optional or not.

XMvn 2.3.0

Major features

• Ownership of generated directories

  XMvn Install 2.3.0 generates RPM directory ownership (%dir) for
  subdirectories it creates.

• Minimal compiler source/target 1.6

  XMvn now enforces source and target values of at least 1.6 in
  Maven Compiler Plugin.

• Deployer optional dependencies

  Metadata format used in 2.3.0 contains new field, which can be
  used to flag any artifact dependency as optional. XMvn deployer
  and installer were modified to set this flag for generated
  metadata.

Minor bugfixes

• Skip generating %attr for symbolic links

  XMvn 2.3.0 doesn't generate RPM file attributes (%attr) for
  symbolic links it creates, which prevents RPM warnings.

Other changes

• Depmap support dropped

  XMvn 2.3.0 removes support for depmaps, which was deprecated for
  some time.

• Dependecy on Java 8

  XMvn now requires Java 8 to run.