2017-06-07 20:15:36 +00:00
|
|
|
// Top-level build file where you can add configuration options common to all
|
|
|
|
// sub-projects/modules.
|
2016-10-05 14:36:59 +00:00
|
|
|
|
|
|
|
buildscript {
|
|
|
|
repositories {
|
|
|
|
jcenter()
|
2017-06-20 15:32:44 +00:00
|
|
|
maven { url 'https://maven.google.com' }
|
2016-10-05 14:36:59 +00:00
|
|
|
}
|
|
|
|
dependencies {
|
2017-10-04 01:44:49 +00:00
|
|
|
classpath 'com.android.tools.build:gradle:3.0.0-beta7'
|
2016-10-05 14:36:59 +00:00
|
|
|
|
|
|
|
// NOTE: Do not place your application dependencies here; they belong
|
2017-06-07 20:15:36 +00:00
|
|
|
// in the individual module build.gradle files.
|
2016-10-05 14:36:59 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
allprojects {
|
|
|
|
repositories {
|
|
|
|
mavenLocal()
|
|
|
|
jcenter()
|
2017-09-12 01:12:11 +00:00
|
|
|
maven { url "https://maven.google.com" } // Required for appcompat.
|
|
|
|
// React Native (JS, Obj-C sources, Android binaries) is installed from
|
|
|
|
// npm.
|
|
|
|
maven { url "$rootDir/../node_modules/react-native/android" }
|
|
|
|
}
|
|
|
|
|
|
|
|
// Third-party react-native modules which Jitsi Meet SDK for Android depends
|
|
|
|
// on and which are not available in third-party Maven repositories need to
|
|
|
|
// be deployed in a Maven repository of ours.
|
|
|
|
//
|
|
|
|
|
|
|
|
if (project.name.startsWith('react-native-')) {
|
|
|
|
apply plugin: 'maven-publish'
|
|
|
|
publishing {
|
|
|
|
publications {}
|
|
|
|
repositories {
|
|
|
|
maven { url "file:${rootProject.projectDir}/../../../jitsi/jitsi-maven-repository/releases" }
|
|
|
|
}
|
2017-08-03 15:40:08 +00:00
|
|
|
}
|
2017-09-12 01:12:11 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
afterEvaluate { project ->
|
|
|
|
if (project.name.startsWith('react-native-')) {
|
|
|
|
def npmManifest = project.file('../package.json')
|
|
|
|
def json = new groovy.json.JsonSlurper().parseText(npmManifest.text)
|
|
|
|
|
|
|
|
// React Native modules have an npm peer dependency on react-native,
|
|
|
|
// they do not have an npm dependency on it. Further below though we
|
|
|
|
// choose a react-native version (range) when we represent them as
|
|
|
|
// Maven artifacts. Effectively, we are forking the projects by not
|
|
|
|
// complying with the full range of their npm peer dependency and,
|
|
|
|
// consequently, we should qualify their version.
|
|
|
|
def versionQualifier = '-jitsi-1'
|
|
|
|
if ('react-native-webrtc'.equals(project.name))
|
|
|
|
versionQualifier = '-jitsi-1'
|
|
|
|
|
|
|
|
project.version = "${json.version}${versionQualifier}"
|
|
|
|
|
|
|
|
project.android {
|
|
|
|
compileSdkVersion rootProject.ext.compileSdkVersion
|
2017-10-04 01:44:49 +00:00
|
|
|
if (rootProject.ext.has('buildToolsVersion')) {
|
|
|
|
buildToolsVersion rootProject.ext.buildToolsVersion
|
|
|
|
}
|
2017-09-12 01:12:11 +00:00
|
|
|
defaultConfig {
|
|
|
|
minSdkVersion rootProject.ext.minSdkVersion
|
|
|
|
targetSdkVersion rootProject.ext.targetSdkVersion
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
task androidJavadocs(type: Javadoc) {
|
|
|
|
source = android.sourceSets.main.java.source
|
|
|
|
classpath += project.files(android.getBootClasspath().join(File.pathSeparator))
|
|
|
|
failOnError false
|
|
|
|
}
|
|
|
|
task androidJavadocsJar(type: Jar, dependsOn: androidJavadocs) {
|
|
|
|
classifier = 'javadoc'
|
|
|
|
from androidJavadocs.destinationDir
|
|
|
|
}
|
|
|
|
task androidSourcesJar(type: Jar) {
|
|
|
|
classifier = 'sources'
|
|
|
|
from android.sourceSets.main.java.source
|
|
|
|
}
|
|
|
|
|
|
|
|
publishing.publications {
|
|
|
|
aarArchive(MavenPublication) {
|
|
|
|
groupId rootProject.ext.moduleGroupId
|
|
|
|
artifactId project.name
|
|
|
|
version project.version
|
|
|
|
|
|
|
|
artifact("${project.buildDir}/outputs/aar/${project.name}-release.aar") {
|
|
|
|
extension "aar"
|
|
|
|
}
|
|
|
|
artifact(androidSourcesJar)
|
|
|
|
artifact(androidJavadocsJar)
|
|
|
|
pom.withXml {
|
|
|
|
def pomXml = asNode()
|
|
|
|
pomXml.appendNode('name', project.name)
|
|
|
|
pomXml.appendNode('description', json.description)
|
|
|
|
pomXml.appendNode('url', json.homepage)
|
|
|
|
if (json.license) {
|
|
|
|
def license = pomXml.appendNode('licenses').appendNode('license')
|
|
|
|
license.appendNode('name', json.license)
|
|
|
|
license.appendNode('distribution', 'repo')
|
|
|
|
}
|
|
|
|
|
|
|
|
def dependencies = pomXml.appendNode('dependencies')
|
|
|
|
configurations.getByName('releaseCompileClasspath').getResolvedConfiguration().getFirstLevelModuleDependencies().each {
|
|
|
|
def artifactId = it.moduleName
|
|
|
|
def version = it.moduleVersion
|
|
|
|
// React Native signals breaking changes by
|
|
|
|
// increasing the minor version number. So the
|
|
|
|
// (third-party) React Native modules we utilize can
|
|
|
|
// depend not on a specific react-native release but
|
|
|
|
// a wider range.
|
|
|
|
if (artifactId.equals('react-native')) {
|
|
|
|
def versionNumber = VersionNumber.parse(version)
|
|
|
|
version = "${versionNumber.major}.${versionNumber.minor}"
|
|
|
|
}
|
|
|
|
|
|
|
|
def dependency = dependencies.appendNode('dependency')
|
|
|
|
dependency.appendNode('groupId', it.moduleGroup)
|
|
|
|
dependency.appendNode('artifactId', artifactId)
|
|
|
|
dependency.appendNode('version', version)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2016-10-05 14:36:59 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
[RN] Add initial Jitsi Meet SDK for Android
Dames en heren, welcome to Jitsi Meet SDK for Android, the Jitsi Meet library
for Android.
The Jitsi Meet SDK encapsulates React Native and all the dependencies Jitsi
Meet has so other aopplications can integrate it easily.
Unlike iOS, creating "fat" libraries is not allways (if at all) possible on
Android, however, effort was put into making the integration as easy as
possible.
While React Native can be embedded in native applications, I don't think it was
designed to be embedded as part of an Android library, hidden away from the
application using it. This surfaced as a number of issues which had to be
addressed specifically due to our use-case:
- Activity lifecycle methods must be linked with the React Native engine, so the
library provides wrapper methods.
- Custom fonts have to be manually added as assets, since the provided gradle
script doesn't work properly in a library target.
- The RN packager has to be manually triggered since the gradle script will no
longer do it for us.
At this stage, the Jitsi Meet application is just a small single activity
application which uses the Jitsi Meet SDK to create a single activity which
represents the entire application. Events and external conference handling are
forthcoming.
PS: Yours truly would like to add that it was a lot more fun to work on the iOS
side of things.
2017-05-22 13:33:42 +00:00
|
|
|
|
|
|
|
ext {
|
2017-06-28 08:51:08 +00:00
|
|
|
compileSdkVersion = 25
|
[RN] Add initial Jitsi Meet SDK for Android
Dames en heren, welcome to Jitsi Meet SDK for Android, the Jitsi Meet library
for Android.
The Jitsi Meet SDK encapsulates React Native and all the dependencies Jitsi
Meet has so other aopplications can integrate it easily.
Unlike iOS, creating "fat" libraries is not allways (if at all) possible on
Android, however, effort was put into making the integration as easy as
possible.
While React Native can be embedded in native applications, I don't think it was
designed to be embedded as part of an Android library, hidden away from the
application using it. This surfaced as a number of issues which had to be
addressed specifically due to our use-case:
- Activity lifecycle methods must be linked with the React Native engine, so the
library provides wrapper methods.
- Custom fonts have to be manually added as assets, since the provided gradle
script doesn't work properly in a library target.
- The RN packager has to be manually triggered since the gradle script will no
longer do it for us.
At this stage, the Jitsi Meet application is just a small single activity
application which uses the Jitsi Meet SDK to create a single activity which
represents the entire application. Events and external conference handling are
forthcoming.
PS: Yours truly would like to add that it was a lot more fun to work on the iOS
side of things.
2017-05-22 13:33:42 +00:00
|
|
|
minSdkVersion = 16
|
2017-08-03 15:44:52 +00:00
|
|
|
targetSdkVersion = 25
|
2017-09-12 01:12:11 +00:00
|
|
|
|
|
|
|
// The Maven artifact groupdId of the third-party react-native modules which
|
|
|
|
// Jitsi Meet SDK for Android depends on and which are not available in
|
|
|
|
// third-party Maven repositories so we have to deploy to a Maven repository
|
|
|
|
// of ours.
|
|
|
|
moduleGroupId = 'com.facebook.react'
|
[RN] Add initial Jitsi Meet SDK for Android
Dames en heren, welcome to Jitsi Meet SDK for Android, the Jitsi Meet library
for Android.
The Jitsi Meet SDK encapsulates React Native and all the dependencies Jitsi
Meet has so other aopplications can integrate it easily.
Unlike iOS, creating "fat" libraries is not allways (if at all) possible on
Android, however, effort was put into making the integration as easy as
possible.
While React Native can be embedded in native applications, I don't think it was
designed to be embedded as part of an Android library, hidden away from the
application using it. This surfaced as a number of issues which had to be
addressed specifically due to our use-case:
- Activity lifecycle methods must be linked with the React Native engine, so the
library provides wrapper methods.
- Custom fonts have to be manually added as assets, since the provided gradle
script doesn't work properly in a library target.
- The RN packager has to be manually triggered since the gradle script will no
longer do it for us.
At this stage, the Jitsi Meet application is just a small single activity
application which uses the Jitsi Meet SDK to create a single activity which
represents the entire application. Events and external conference handling are
forthcoming.
PS: Yours truly would like to add that it was a lot more fun to work on the iOS
side of things.
2017-05-22 13:33:42 +00:00
|
|
|
}
|
2017-06-20 15:32:44 +00:00
|
|
|
|
|
|
|
// Force the version of the Android build tools we have chosen on all
|
|
|
|
// subprojects. The forcing was introduced for react-native and the third-party
|
|
|
|
// modules that we utilize such as react-native-background-timer.
|
|
|
|
subprojects { subproject ->
|
|
|
|
afterEvaluate{
|
2017-10-04 01:44:49 +00:00
|
|
|
if ((subproject.plugins.hasPlugin('android')
|
|
|
|
|| subproject.plugins.hasPlugin('android-library'))
|
|
|
|
&& rootProject.ext.has('buildToolsVersion')) {
|
2017-06-20 15:32:44 +00:00
|
|
|
android {
|
|
|
|
buildToolsVersion rootProject.ext.buildToolsVersion
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|