Step 1. Add the JitPack repository to your build file
Add it in your root settings.gradle at the end of repositories:
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
mavenCentral()
maven { url 'https://jitpack.io' }
}
}
Add it in your settings.gradle.kts at the end of repositories:
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
mavenCentral()
maven { url = uri("https://jitpack.io") }
}
}
Add to pom.xml
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
Add it in your build.sbt at the end of resolvers:
resolvers += "jitpack" at "https://jitpack.io"
Add it in your project.clj at the end of repositories:
:repositories [["jitpack" "https://jitpack.io"]]
Step 2. Add the dependency
dependencies {
implementation 'com.github.nuborisar:realm-java:'
}
dependencies {
implementation("com.github.nuborisar:realm-java:")
}
<dependency>
<groupId>com.github.nuborisar</groupId>
<artifactId>realm-java</artifactId>
<version></version>
</dependency>
libraryDependencies += "com.github.nuborisar" % "realm-java" % ""
:dependencies [[com.github.nuborisar/realm-java ""]]
Realm is a mobile database that runs directly inside phones, tablets or wearables. This repository holds the source code for the Java version of Realm, which currently runs only on Android.
Please see the detailed instructions in our docs to add Realm to your project.
Documentation for Realm can be found at realm.io/docs/java. The API reference is located at realm.io/docs/java/api.
If you want to test recent bugfixes or features that have not been packaged in an official release yet, you can use a -SNAPSHOT release of the current development version of Realm via Gradle, available on OJO
buildscript {
repositories {
maven {
url 'http://oss.jfrog.org/artifactory/oss-snapshot-local'
}
}
dependencies {
classpath "io.realm:realm-gradle-plugin:<version>-SNAPSHOT"
}
}
repositories {
maven {
url 'http://oss.jfrog.org/artifactory/oss-snapshot-local'
}
}
See version.txt for the latest version number.
In case you don't want to use the precompiled version, you can build Realm yourself from source.
Prerequisites:
make
is available in your $PATH
Or you can use Hombrew-versions to install Android NDK for Mac:
brew tap homebrew/versions
brew install android-ndk-r10e
Add two environment variables to your profile:
export ANDROID_HOME=~/Library/Android/sdk
export NDK_HOME=/usr/local/Cellar/android-ndk-r10e/r10e
If you are using OS X, you'd be better to add following lines to ~/.profile
(or ~/.zprofile
if the login shell is zsh
) in order for Android Studio to see those environment variables.
launchctl setenv ANDROID_HOME "$ANDROID_HOME"
launchctl setenv NDK_HOME "$NDK_HOME"
And if you'd like to specify the location to store the archives of Realm's core, set REALM_CORE_DOWNLOAD_DIR
environment variable. It enables you to keep core's archive when executing git clean -xfd
.
export REALM_CORE_DOWNLOAD_DIR=~/.realmCore
OS X users should also add following line to ~/.profile
(or ~/.zprofile
if the login shell is zsh
) in order for Android Studio to see this environment variable..
launchctl setenv REALM_CORE_DOWNLOAD_DIR "$REALM_CORE_DOWNLOAD_DIR"
Once you have completed all the pre-requisites building Realm is done with a simple command
./gradlew assemble
That command will generate:
./gradlew tasks
will show all the available tasks./gradlew javadoc
will generate the Javadocs./gradlew monkeyExamples
will run the monkey tests on all the examples./gradlew installRealmJava
will install the Realm library and plugin to mavenLocal()./gradlew clean -PdontCleanJniFiles
will remove all generated files except for JNI related files. This saves recompilation time a lot../gradlew connectedUnitTests -PbuildTargetABIs=$(adb shell getprop ro.product.cpu.abi)
will build JNI files only for the ABI which corresponds to the connected device.Generating the Javadoc using the command above will report a large number of warnings. The Javadoc is generated, and we will fix the issue in the near future.
The repository is organized in six Gradle projects:
realm
: it contains the actual library (including the JNI layer) and the annotations processor.realm-annotations
: it contains the annotations defined by Realm.realm-transformer
: it contains the bytecode transformer.gradle-plugin
: it contains the Gradle plugin.examples
: it contains the example projects. This project directly depends on gradle-plugin
which adds a dependency to the artifacts produced by realm
.This means that ./gradlew clean
and ./gradlew cleanExamples
will fail if assembleExamples
has not been executed first.
Note that IntelliJ does not support multiple projects in the same window
so each sub-project must be opened in its own window.
The ./examples
folder contain a number of example projects showing how Realm can be used. If this is the first time you checkout or pull a new version of this repository to try the examples, you must call ./gradlew installRealmJava
from the top-level directory first. Otherwise the examples will not compile as they depend on all Realm artifacts being installed in mavenLocal()
.
Standalone examples can be downloaded from website.
See CONTRIBUTING.md for more details!
This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to info@realm.io.
Realm Java is published under the Apache 2.0 license. The underlying core is available under the Realm Core Binary License while we work to open-source it under the Apache 2.0 license.
This product is not being made available to any person located in Cuba, Iran, North Korea, Sudan, Syria or the Crimea region, or to any other person that is not eligible to receive the product under U.S. law.
If you use Realm and are happy with it, all we ask is that you please consider sending out a tweet mentioning @realm, announce your app on our mailing-list, or email help@realm.io to let us know about it!
And if you don't like it, please let us know what you would like improved, so we can fix it!