[jitsi-dev] Use Ivy or Maven to manage java dependencies


#1

I've filled this issue already as JITSI-994 without knowing your procedures.
Please reopen this issue if you want to solve it.

It is hard for a distro (Debian/Fedora/Suse) packager to find out which java
dependencies Jitsi has. A pom.xml or ivy.xml would make things much easier and
then the dependencies could also be removed from SVN.

Thomas Koch, http://www.koch.ro


#2

Hey

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.

Two problems though are not solved with that:
- Patches (like in Smack)
- Libraries not available in MVN-Repos (like lcrypro on Werner's or my own GitHub page, sdes4j, and probably many others)

Ivy in general is very simple. Place an ivy.xml into the project, add the lib-references, add an ivy-task into build.xml (9 lines). And for Eclipse users, the same ivy.xml can be used by the plugin IvyDE. It adds a Library Container to the project's build-path.

I might take a look into this once the DNSSEC stuff is over - which leads to early next year.

@Thomas: You might want to start with an ivy.xml (as described above), we happily apply patches.

cu,
Ingo

ยทยทยท

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Dienstag, 22. November 2011 22:40
To: thomas@koch.ro
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Use Ivy or Maven to manage java dependencies
Sounds interesting. Would happily review a patch.

Emil

--sent from my mobile

On 22 nov. 2011, at 17:09, Thomas Koch <thomas@koch.ro> wrote:

I've filled this issue already as JITSI-994 without knowing your
procedures. Please reopen this issue if you want to solve it.

It is hard for a distro (Debian/Fedora/Suse) packager to find out which
java dependencies Jitsi has. A pom.xml or ivy.xml would make things
much easier and then the dependencies could also be removed from SVN.

Thomas Koch, http://www.koch.ro


#3

Bauersachs Ingo:

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
advice.

Regards,

Thomas Koch, http://www.koch.ro