[jitsi-dev] [libjitsi] Created pom.xml (#19)


#1

The downside is that some of the libraries must be provided in project lib directory because they are unavailable from a repo and / or they are specially modified for jitsi.
You can merge this Pull Request by running:

  git pull https://github.com/mondain/libjitsi patch-1

Or you can view, comment on it, or merge it online at:

  https://github.com/jitsi/libjitsi/pull/19

-- Commit Summary --

  * Created pom.xml

-- File Changes --

    A pom.xml (305)

-- Patch Links --

https://github.com/jitsi/libjitsi/pull/19.patch
https://github.com/jitsi/libjitsi/pull/19.diff

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19


#2

+1 for mavenization of Jitsi for what it's worth.

I'm not so sure I agree with the proposed pom.xml though. Jitsi is composed of multiple OSGi bundles and I would like to see 1 maven module per OSGi bundle and one Maven aggregator module for Jitsi as a whole.

I've done that for bundles (and their dependencies) that are used in Jitsi Videobridge and in JICOFO (our server side focus).

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-65898385


#3

@gpolitis Yes, that was what I meant with cleaning :-). And I'm all in for one project per bundle and a parent project. That will be a lot of work though and I'd start as simple as possible - making libjitsi a Maven project before even attempting to do something with Jitsi itself.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-65899096


#4

The pom is meant as a transition to maven; I personally don't have experience with OSGI, but I have done modular maven poms.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-65900896


#5

duh, I'm sorry, I though this was a pull request for Jitsi the client. I now realise that it's for libjitsi, sorry again. I think this is a great start then!

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-65934849


#6

I have tried to cleanup a bit my Jitsi mavenization scripts and since there seems to be others interested in mavenizing Jitsi, I decided to push them [here](https://github.com/gpolitis/jitsi-mavenization).

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-66984218


#7

I started working on mavenization. I decided to split java sources to one artifact and create another artifacts for each native lib that should be compiled to so and dll.

Here is java part https://github.com/stokito/libjitsi/tree/maven
Native part https://github.com/stokito/libjitsi/tree/maven-native

Then I found that some libraries may be duplicated with other JNI bindings.
For example, official VPX repository already have JNI binding, but it looks obsolete https://code.google.com/p/webm/source/browse/?repo=bindings
So I decided to make it as separate repostitory [libjnvpx](https://github.com/stokito/libjnvpx) and merge with official binding.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-69132548


#8

Maven is now supported with @lyubomir 's 8c139bf0f1784eca2da01bf48b8349ce60d99135.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#issuecomment-122926173


#9

Closed #19.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/libjitsi/pull/19#event-360147046