Commit 2328c389 authored by Erwan Croze's avatar Erwan Croze 👋🏻

Fix markdown syntax

parent 78472d01
= Introduction = # Introduction
Until today, integrating liblinphone sdk into a third party application required compiling a sdk from the sources or importing sdk binary files from: http://www.linphone.org/technical-corner/liblinphone/downloads Until today, integrating liblinphone sdk into a third party application required compiling a sdk from the sources or importing sdk binary files from: http://www.linphone.org/technical-corner/liblinphone/downloads
In order to ease integration of this sdk, we adapted a Gitlab repository as a Maven one. In order to ease integration of this sdk, we adapted a Gitlab repository as a Maven one.
...@@ -7,11 +6,11 @@ Maven is a standardized tool to manage and build Java-based projects, which core ...@@ -7,11 +6,11 @@ Maven is a standardized tool to manage and build Java-based projects, which core
With Gradle and this Maven repository, we now offer the ability to either host or import remotely liblinphone sdk, as any future library. With Gradle and this Maven repository, we now offer the ability to either host or import remotely liblinphone sdk, as any future library.
= How to produce and host Liblinphone SDK on our Maven repository = # How to produce and host Liblinphone SDK on our Maven repository
To host Liblinphone SDK and allow future remote import, follow theses steps: To host Liblinphone SDK and allow future remote import, follow theses steps:
== Get Linphone-Android and deploy locally Liblinphone SDK == ## Get Linphone-Android and deploy locally Liblinphone SDK
git clone git@gitlab.linphone.org:BC/public/linphone-android.git git clone git@gitlab.linphone.org:BC/public/linphone-android.git
...@@ -22,12 +21,12 @@ To host Liblinphone SDK and allow future remote import, follow theses steps: ...@@ -22,12 +21,12 @@ To host Liblinphone SDK and allow future remote import, follow theses steps:
== Binary and Maven files production == ## Binary and Maven files production
This part requires a private SSH key used to write right to the repository, it must be asked to Simon Morlat, Jehan Monnier, Sylvain Berfini or Erwan Croze. This part requires a private SSH key used to write right to the repository, it must be asked to Simon Morlat, Jehan Monnier, Sylvain Berfini or Erwan Croze.
Then it must be placed into liblinphone-sdk folder. Then it must be placed into liblinphone-sdk folder.
=== Settings === ### Settings
Set the liblinphone-sdk/build.gradle and gradle.properties files as in the maven_repository Git project. Set the liblinphone-sdk/build.gradle and gradle.properties files as in the maven_repository Git project.
...@@ -73,7 +72,7 @@ gradle.properties: ...@@ -73,7 +72,7 @@ gradle.properties:
privateKey=./maven_rsa privateKey=./maven_rsa
=== Options explanation === ### Options explanation
-configuration: uses settings and deployment forms from wagon-git project, which allows gradle to push right to maven_repository. -configuration: uses settings and deployment forms from wagon-git project, which allows gradle to push right to maven_repository.
...@@ -83,13 +82,13 @@ gradle.properties: ...@@ -83,13 +82,13 @@ gradle.properties:
-pom.project: theses options will define the way we call the dependency in the last part, as following: -pom.project: theses options will define the way we call the dependency in the last part, as following:
'groupId:artifactId:version' 'groupId:artifactId:version'
For other libraries or versions, just edit artifactId or version. For other libraries or versions, just edit artifactId or version.
Keep the -DEBUG part in the code. Maven favors convention over configuration. Keep the -DEBUG part in the code. Maven favors convention over configuration.
=== Production === ### Production
Check if linphone-android builds on the right device. Check if linphone-android builds on the right device.
Then, in a terminal located at linphone-android's root, type: Then, in a terminal located at linphone-android's root, type:
...@@ -105,12 +104,12 @@ Then, in a terminal located at linphone-android's root, type: ...@@ -105,12 +104,12 @@ Then, in a terminal located at linphone-android's root, type:
Warning: If a not working version is produced, before building it again, clear the whole gradle cache ($HOME/.gradle/caches/), or gradle will produce the same. Warning: If a not working version is produced, before building it again, clear the whole gradle cache ($HOME/.gradle/caches/), or gradle will produce the same.
= How to use hosted Liblinphone SDK as a remote dependency = # How to use hosted Liblinphone SDK as a remote dependency
In another linphone-android project, in which you can delete liblinphone-sdk folder, edit linphone-android build.gradle like the one located in maven_repository root: In another linphone-android project, in which you can delete liblinphone-sdk folder, edit linphone-android build.gradle like the one located in maven_repository root:
== Set our Maven repository source == ## Set our Maven repository source
allprojects { allprojects {
...@@ -124,7 +123,7 @@ In another linphone-android project, in which you can delete liblinphone-sdk fol ...@@ -124,7 +123,7 @@ In another linphone-android project, in which you can delete liblinphone-sdk fol
Be sure to keep the raw/master part in future modification, as it defines the true path to files, not the one to navigate in web browser. Be sure to keep the raw/master part in future modification, as it defines the true path to files, not the one to navigate in web browser.
== Change our local project dependency to remote dependency == ## Change our local project dependency to remote dependency
dependencies { dependencies {
...@@ -137,11 +136,11 @@ Be sure to keep the raw/master part in future modification, as it defines the tr ...@@ -137,11 +136,11 @@ Be sure to keep the raw/master part in future modification, as it defines the tr
Comment release or debug line if no remote library is available for it. Comment release or debug line if no remote library is available for it.
Use the settings provided in the creation part so gradle can find the right dependency: Use the settings provided in the creation part so gradle can find the right dependency:
'groupId:artifactId:version' 'groupId:artifactId:version'
In case of another library need or newer version, provided it is hosted, just change artifactId and version in accordance to its declaration in the creation part. In case of another library need or newer version, provided it is hosted, just change artifactId and version in accordance to its declaration in the creation part.
= Sources = # Sources
All of these links contributed to teach me the way to produce this repository: All of these links contributed to teach me the way to produce this repository:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment