Commit 70522302 authored by George Nash's avatar George Nash Committed by Kishen Maloor

Update URLs to point to new gitlab tools

When the project was moved from gerrit and jenkens there
were locations in the README files that the new paths
were not updated. This change updates those URLs.

Also improves a few other locations in the text.
Signed-off-by: George Nash's avatarGeorge Nash <george.nash@intel.com>
parent 60138901
......@@ -23,7 +23,7 @@ It can be installed on Ubuntu Linux using the following command.
Checkout IoTivity-lite git project run the following command to get a anonymous copy of
iotivity-lite. Checkout the SWIG branch.
git clone https://gerrit.iotivity.org/gerrit/iotivity-lite
git clone https://gitlab.iotivity.org/iotivity/iotivity-lite.git
### Android SDK tools
Download the [Android SDK command line tools](https://developer.android.com/studio#downloads)
......@@ -102,8 +102,8 @@ Building and Running Samples
-------------------------------------------------
All samples have the default out of the box behavior of IoTivity-Lite which means they are are not
onboarded or provisioned. The default security will prevent the samples from communicating with
one another till onboarding and provisioning has been completed. See the following section
**Onboarding and Provisioning** for instructions on using the onboarding tool that is part of
one another till onboarding and provisioning has been completed. See **Onboarding and Provisioning**
section of the top level README file for instructions on using the onboarding tool that is part of
iotivity-lite.
A sample server and client can be found in `<iotivity-lite>/swig/apps/<sample>`
......@@ -155,9 +155,9 @@ README for step-by-step instructions to onboard and test the samples.
Building Custom Android Applications
-------------------------------------------------
These libraries and examples were built with Android API 23. When creating a new Android project you
can choose the API level. In building these examples, the native code libraries were copied to specific
directories in the project. The project structure is:
These libraries and examples were built with Android API 23. When creating a new Android project a
different API level may be chosen. When building these examples, the native code libraries were
copied to specific directories in the project. The project structure is:
```
project/
......@@ -204,7 +204,8 @@ This structure is reflected in the app `build.gradle` file:
}
```
To allow these example applications to work, permissions had to be granted in the `AndroidManifest.xml` file.
To allow these example applications to work, permissions had to be granted in the
`AndroidManifest.xml` file.
```
<manifest ...>
......@@ -228,7 +229,7 @@ To allow these example applications to work, permissions had to be granted in th
Send Feedback
-------------------------------------------------
Questions
[IoTivity-Lite Developer Mailing List](https://iotivity-dev@lists.iotivity.org)
[IoTivity-Lite Developer Mailing List](https://iotivity.groups.io/g/iotivity-dev)
Bugs
[Jira bug reporting website](https://jira.iotivity.org/projects/LITE)
[IoTivity-lite gitlab issues](https://gitlab.iotivity.org/iotivity/iotivity-lite/issues)
......@@ -31,7 +31,7 @@ Due to licensing changes the output is no longer tested against Oracle Java.
Currently SWIG version 3.0 is recommended. SWIG version 4.0 came out during the development of the
Java language bindings. Users are welcome to use a newer version as long as they are aware it has
not been tested.
not been as extensively tested.
Instructions for Android
-------------------------------------------------
......@@ -49,22 +49,15 @@ Instructions for Linux
Checkout IoTivity-Lite git project run the following command to get a anonymous copy of
iotivity-lite. Checkout the SWIG branch.
git clone https://gerrit.iotivity.org/gerrit/iotivity-lite
git clone https://gitlab.iotivity.org/iotivity/iotivity-lite.git
If you are behind a proxy setup the git proxy settings before running the above commands
git config --global http.proxy http://<username>:<password>@<proxy-server-url>:<port>
Since this is an anonymous download you will not be able to push any changes up to the project.
IoTivity is managed by the Linux Foundation. If you are planning on contributing back to
IoTivity you will need to have a [Linux Foundation ID](https://identity.linuxfoundation.org/).
The Linux Foundation ID can then be used to log into the Gerrit server for IoTivity-Lite.
[gerrit.iotivity.org](https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity-lite)
Follow the instructions [here](https://wiki.iotivity.org/how_to_use_gerrit) to gain push access
to the project.
If you are planning on contributing back to IoTivity you will need to make a gitlab account and
request developer access to the iotivity-lite project.
### Build Java language bindings
Navigate to `<iotivity-lite>/port/linux`
......@@ -113,8 +106,8 @@ Instructions for Windows
been tested in newer versions of Visual Studio and have been found to work. Visual studio IDE
Community edition and Visual Studio Code should work but have not personally been tested.
Set JAVA_HOME environment variable to point to the Java Development kit. This is required so Make
can find the jni.h header files.
Set JAVA_HOME environment variable to point to the Java Development kit. This is required so the
build can find the jni.h header files.
### Build Java language bindings
Build the JNI shared library:
......@@ -345,7 +338,7 @@ If JAVA_HOME is not found add it to your environment variables.
Send Feedback
-------------------------------------------------
Questions
[IoTivity-Lite Developer Mailing List](https://iotivity-dev@lists.iotivity.org)
[IoTivity-Lite Developer Mailing List](https://iotivity.groups.io/g/iotivity-dev)
Bugs
[Jira bug reporting website](https://jira.iotivity.org/projects/LITE)
[IoTivity-lite gitlab issues](https://gitlab.iotivity.org/iotivity/iotivity-lite/issues)
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