= Proposed Self Contained Change: Improved Ivy Packaging =
Change owner(s): Mikolaj Izdebski <mizdebsk(a)redhat.com>
This change aims at improving the way of packaging Java software, which uses
Apache Ivy to manage build dependencies.
== Detailed Description ==
Currently packages which use Apache Ivy as dependency manager are packaged in
manual way. Dependencies must be symlinked manually, all files have to be
explicitly installed, there are no auto-requires.
This change aims at simplifying Ivy packaging in a similar way as it was done
with Maven packaging .
In particular, the following changes will be implemented:
* automatic resolution of Ivy artifacts,
* integration with system Maven repository,
* automatic installation of Ivy artifact metadata,
* auto requires.
== Scope ==
* Implement code to resolve and publish Ivy artifacts in XMvn upstream
* Package new upstream version XMvn in Fedora or backport Ivy changes to
current XMvn version
* Implement necessary macros in Javapackages Tools upstream
* Package new upstream version Javapackages Tools in Fedora or backport
necessary changes to current Javapackages Tools version
* Prepare draft of Java packaging guidelines change and submit to FPC
* Maintainers of packages using Apache Ivy during build or installing Ivy
artifacts can optionally update their packages to use the new packaging
techniques, but that's not absolutely required as existing ways of packaging
Ivy artifacts will continue to work.
* No action required.
Policies and guidelines:
* Java packaging guidelines will have to be updated to include the new way of
packaging Ivy artifacts.