I'm planning to merge the mead branch into the master koji branch in the
near future. This branch contains the changes that allow Koji to handle
Maven builds (still within a mock chroot) and track the resulting
(non-rpm) output. We've kept this work on a separate branch for over two
years and the code is stable.
Of course, not everyone wants to allow Maven builds in their Koji
instance. As part of the merge, we will add controls that allow the
Maven functionality to be disabled.
If you have any comments or concerns, please let me know.
Show replies by date