Skip to content

jaragunde/owncloud-android-library

 
 

Repository files navigation

ownCloud Android Library

Introduction

Using ownCloud Android library it will be the easiest way to communicate with ownCloud servers. Add this library in your project and integrate your application with ownCloud seamlessly.

This fork includes all dependencies in source form, removing any binary jars.

Install Library

2.1. Information how to get the library

Get this code and compile it. In the repository it is not only the library project but also the example project “sample_client”; thanks to it you will learn how to use the library.

2.2. Add library to your project

There are different ways of adding this library to your code, then it is described one of them

Step 1. Compile the ownCloud Android Library Step 2. Define a dependency within your project. For that, access to Properties > Android > Library and click on add and select the ownCloud Android library

Branching strategy

The repository holds two main branches with an infinite lifetime:

  • master
  • develop

Branch origin/master is considered the main branch where the source code of HEAD always reflects a production-ready state.

Branch origin/develop is considered the main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release.

When the source code in the develop branch reaches a stable point and is ready to be released, all of the changes should be merged back into master somehow and then tagged with a release number.

Other branches, some supporting branches are used to aid parallel development between team members, ease tracking of features, prepare for production releases and to assist in quickly fixing live production problems. Unlike the main branches, these branches always have a limited life time, since they will be removed eventually.

The different types of branches we may use are:

  • Branch perNewFeature
  • Branch releaseBranches

Both of them branch off from develop and must merge back into develop branch through a Pull Request in Github. Once the PR is approved and merged, the US branch may be deleted.

Source: http://nvie.com/posts/a-successful-git-branching-model

Brach no-binary-deps

This branch removes binary jar files and replaces them with the source code for any required libraries.

It will be periodically merged with master and tagged with the corresponding version number plus -no-binary-deps.

License

ownCloud Android Library is available under MIT license. See the file LICENSE.md with the full license text.

Third party libraries

This bundle contains source code from the following projects:

  • Apache Commons Codec, version 1.9. Copyright 2002-2013 The Apache Software Foundation. Licensed under Apache License, Version 2.0.

  • Apache Jakarta HttpClient, version 3.1. Copyright 1999-2007 The Apache Software Foundation. Licensed under Apache License, Version 2.0.

  • Apache Jackrabbit, version 2.7.2. Copyright 2013 The Apache Software Foundation. Licensed under Apache License, Version 2.0.

  • SLF4J, version 1.7.12. Copyright (c) 2004-2013 QOS.ch. Distributed under the MIT license.

  • Java Servlet implementation from the Apache Tomcat project, version 7.0.40. Copyright 1999-2013 The Apache Software Foundation. Licensed under Apache License, Version 2.0.

Original license files and copyright notices are under the corresponding directories inside libs/.

Compatibility

ownCloud Android Library is valid for Android systems from version Android 2.2 (android:minSdkVersion="8" android:targetSdkVersion="19").

ownCloud Android library supports ownCloud server from version 4.5.

About

This fork includes all dependencies in source form, removing any binary jars.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 99.3%
  • Other 0.7%