As a start it would be enough to just let Ivy (I don't know Maven) grab the
libs from a local repository (which would be based on the current
installer-exclude). Then the libraries could step-by-step be migrated from
the local folder to an official MVN-Repo.
Yes, going to Ivy first is a good strategy and one can continue to Maven on
top of that later if desired.
Two problems though are not solved with that:
- Patches (like in Smack)
At least it's very important to have such patches documented together with the
reasons for their existence. Even better is to fill an entry in the libraries
issue tracker and work together with them to have the patch included. But I
assume I'm not telling anything new here.
- Libraries not available in MVN-Repos (like lcrypro on Werner's or my own
GitHub page, sdes4j, and probably many others)
I've made the experience that library authors appreciate any help to get their
libraries included in Maven. I could help on this site once the list of not-
yet mavenized dependencies exists.
@Thomas: You might want to start with an ivy.xml (as described above), we
happily apply patches.
I'm afraid I'm already involved in too many projects and can only offer
Thomas Koch, http://www.koch.ro