Benefit to Fedora

After moving packages to start using XMvn instead of current mvn-rpmbuild spec files will be simpler, easier to maintain and modify. Automatic requires generation will make updating packages easier and less error-prone.

Not having to patch Maven will also open door to faster Maven updates.

Scope

Conversion of mvn-rpmbuild spec files to XMvn is mostly trivial removals and simplifications, but we'll be providing recipes for most common conversions.

How To Test

Tests are best done by reworking your packages to use XMvn instead of mvn-rpmbuild and then verify that automatically generated requires stayed sane.

User Experience

End-users:

No end-user visible difference

Packagers:

Packagers will likely enjoy simplified spec files

Packagers will nevertheless have to learn new ways to handle Maven packaging. Advantages outweigh this learning curve though.

Dependencies

No dependencies

Contingency Plan

In case some packages can not migrate due to inevitable incompatibilities they can keep using mvn-rpmbuild and ignore automatic requires.

Documentation

Recipes for conversion from old mvn-rpmbuild to XMvn are being prepared [1].