Skip to content
This repository was archived by the owner on Dec 29, 2022. It is now read-only.

Commit 36978d6

Browse files
authored
Remove android from geofire-java (#152)
2 parents c46ff33 + 813d8c0 commit 36978d6

32 files changed

Lines changed: 200 additions & 874 deletions

File tree

.travis.yml

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,13 @@
1-
language: android
1+
language: java
22
jdk: oraclejdk8
33
sudo: required
4-
before_install:
5-
- mkdir "$ANDROID_HOME/licenses" || true
6-
- echo -e "\n8933bad161af4178b1185d1a37fbf41ea5269c55" > "$ANDROID_HOME/licenses/android-sdk-license"
7-
- echo -e "\n84831b9409646a918e30573bab4c9c91346d8abd" > "$ANDROID_HOME/licenses/android-sdk-preview-license"
8-
android:
9-
components:
10-
- tools
11-
- tools
12-
- platform-tools
13-
- android-27
14-
- build-tools-27.0.2
154
before_cache:
165
- rm -f $HOME/.gradle/caches/modules-2/modules-2.lock
176
- rm -fr $HOME/.gradle/caches/*/plugin-resolution/
187
cache:
198
directories:
209
- "$HOME/.gradle/caches/"
2110
- "$HOME/.gradle/wrapper/"
22-
- "$HOME/.android/build-cache"
23-
before_script:
24-
- echo y | ${ANDROID_HOME}/tools/bin/sdkmanager --channel=3 "tools" "platform-tools"
25-
"build-tools;27.0.2" "platforms;android-27" "extras;google;m2repository"
2611
script: "./build.sh"
2712
java/service-account:
2813
json:

CONTRIBUTING.md

Lines changed: 168 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,168 @@
1+
# Contributing
2+
3+
We'd love for you to contribute to our source code and to make it even better than it is today! Here are the guidelines we'd like you to follow:
4+
5+
- [Code of Conduct](#coc)
6+
- [Question or Problem?](#question)
7+
- [Issues and Bugs](#issue)
8+
- [Feature Requests](#feature)
9+
- [Submission Guidelines](#submit)
10+
- [Coding Rules](#rules)
11+
- [Signing the CLA](#cla)
12+
13+
## <a name="coc"></a> Code of Conduct
14+
15+
As contributors and maintainers of the project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
16+
17+
Communication through any of Firebase's channels (GitHub, StackOverflow, Google+, Twitter, etc.) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
18+
19+
We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the project to do the same.
20+
21+
If any member of the community violates this code of conduct, the maintainers of the project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.
22+
23+
If you are subject to or witness unacceptable behavior, or have any other concerns, please drop us a line at nivco@google.com.
24+
25+
## <a name="question"></a> Got a Question or Problem?
26+
27+
If you have questions about how to use the project, please direct these to [StackOverflow][stackoverflow] and use the `firebase` tag. We are also available on GitHub issues.
28+
29+
If you feel that we're missing an important bit of documentation, feel free to
30+
file an issue so we can help. Here's an example to get you started:
31+
32+
```
33+
What are you trying to do or find out more about?
34+
35+
Where have you looked?
36+
37+
Where did you expect to find this information?
38+
```
39+
40+
## <a name="issue"></a> Found an Issue?
41+
42+
If you find a bug in the source code or a mistake in the documentation, you can help us by
43+
submitting an issue on this repository. Even better you can submit a Pull Request
44+
with a fix.
45+
46+
See [below](#submit) for some guidelines.
47+
48+
## <a name="submit"></a> Submission Guidelines
49+
50+
### Submitting an Issue
51+
52+
Before you submit your issue search the archive, maybe your question was already answered.
53+
54+
If your issue appears to be a bug, and hasn't been reported, open a new issue.
55+
Help us to maximize the effort we can spend fixing issues and adding new
56+
features, by not reporting duplicate issues. Providing the following information will increase the
57+
chances of your issue being dealt with quickly:
58+
59+
* **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
60+
* **Motivation for or Use Case** - explain why this is a bug for you
61+
* **Browsers and Operating System** - is this a problem with all browsers or only IE9?
62+
* **Reproduce the Error** - provide a live example or an unambiguous set of steps.
63+
* **Related Issues** - has a similar issue been reported before?
64+
* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
65+
causing the problem (line of code or commit)
66+
67+
**If you get help, help others. Good karma rulez!**
68+
69+
Here's a template to get you started:
70+
71+
```
72+
System information (OS, Device, etc):
73+
74+
What steps will reproduce the problem:
75+
1.
76+
2.
77+
3.
78+
79+
What is the expected result?
80+
81+
What happens instead of that?
82+
83+
Code, logs, or screenshot that illustrate the problem:
84+
```
85+
86+
### Submitting a Pull Request
87+
Before you submit your pull request consider the following guidelines:
88+
89+
* Search for an open or closed Pull Request
90+
that relates to your submission. You don't want to duplicate effort.
91+
* Please sign our [Contributor License Agreement (CLA)](#cla) before
92+
sending pull requests. We cannot accept code without this.
93+
* Make your changes in a new git branch:
94+
95+
```shell
96+
git checkout -b my-fix-branch master
97+
```
98+
99+
* Create your patch, **including appropriate test cases**.
100+
* Follow our [Coding Rules](#rules).
101+
* Commit your changes using a descriptive commit message.
102+
103+
```shell
104+
git commit -a
105+
```
106+
Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
107+
108+
* Push your branch to GitHub:
109+
110+
```shell
111+
git push origin my-fix-branch
112+
```
113+
114+
* In GitHub, send a pull request to `master`.
115+
* If we suggest changes then:
116+
* Make the required updates.
117+
* Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
118+
119+
```shell
120+
git rebase master -i
121+
git push origin my-fix-branch -f
122+
```
123+
124+
That's it! Thank you for your contribution!
125+
126+
#### After your pull request is merged
127+
128+
After your pull request is merged, you can safely delete your branch and pull the changes
129+
from the main (upstream) repository:
130+
131+
* Delete the remote branch on GitHub either through the GitHub UI or your local shell as follows:
132+
133+
```shell
134+
git push origin --delete my-fix-branch
135+
```
136+
137+
* Check out the master branch:
138+
139+
```shell
140+
git checkout master -f
141+
```
142+
143+
* Delete the local branch:
144+
145+
```shell
146+
git branch -D my-fix-branch
147+
```
148+
149+
* Update your master with the latest upstream version:
150+
151+
```shell
152+
git pull --ff upstream master
153+
```
154+
155+
## <a name="rules"></a> Coding Rules
156+
157+
We generally follow [Google's style guides][style-guide].
158+
159+
## <a name="cla"></a> Signing the CLA
160+
161+
Please sign our [Contributor License Agreement][google-cla] (CLA) before sending pull requests. For any code
162+
changes to be accepted, the CLA must be signed. It's a quick process, we promise!
163+
164+
*This guide was inspired by the [AngularJS contribution guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md).*
165+
166+
[google-cla]: https://cla.developers.google.com
167+
[style-guide]: http://google.github.io/styleguide/
168+
[stackoverflow]: http://stackoverflow.com/questions/tagged/firebase

README.md

Lines changed: 17 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,27 @@
1-
# GeoFire for Android/Java — Realtime location queries with Firebase
1+
# GeoFire for Java — Realtime location queries with Firebase
22

33
[![Build Status](https://travis-ci.org/firebase/geofire-java.svg?branch=master)](https://travis-ci.org/firebase/geofire-java?branch=master)
44

5-
GeoFire is an open-source library for Android/Java that allows you to store and query a
5+
**Note** This library is only for _server side_ Java development. If you want to use GeoFire
6+
in your Android application, see [`geofire-android`](https://github.com/firebase/geofire-android).
7+
8+
GeoFire is an open-source library for Java that allows you to store and query a
69
set of keys based on their geographic location.
710

811
At its heart, GeoFire simply stores locations with string keys. Its main
912
benefit however, is the possibility of querying keys within a given geographic
1013
area - all in realtime.
1114

12-
GeoFire uses the [Firebase](https://www.firebase.com/?utm_source=geofire-java) database for
15+
GeoFire uses the [Firebase Realtime Database](https://firebase.google.com/products/realtime-database/) database for
1316
data storage, allowing query results to be updated in realtime as they change.
1417
GeoFire *selectively loads only the data near certain locations, keeping your
1518
applications light and responsive*, even with extremely large datasets.
1619

17-
A compatible GeoFire client is also available for [Objective-C](https://github.com/firebase/geofire-objc)
18-
and [JavaScript](https://github.com/firebase/geofire-js).
20+
GeoFire clients are also available for other languages:
1921

20-
For a full example of an application using GeoFire to display realtime transit data, see the
21-
[SFVehicles](https://github.com/firebase/geofire-java/tree/master/examples/SFVehicles) example in
22-
Android app in this repo.
22+
* [Android](https://github.com/firebase/geofire-android)
23+
* [Objective-C (iOS)](https://github.com/firebase/geofire-objc)
24+
* [JavaScript (Web)](https://github.com/firebase/geofire-js)
2325

2426
### Integrating GeoFire with your data
2527

@@ -57,28 +59,14 @@ here](https://github.com/firebase/geofire-js/blob/master/examples/securityRules/
5759
and [read our docs for more information about indexing your data](https://www.firebase.com/docs/security/guide/indexing-data.html).
5860

5961

60-
## Including GeoFire in your project Android/Java
61-
62-
In order to use GeoFire in your project, you need to [add the Firebase Android
63-
SDK](https://firebase.google.com/docs/android/setup). After that you can include GeoFire with one of the choices below.
62+
## Including GeoFire in your Java project
6463

65-
Note that after version `1.1.1` the artifact `com.firebase:geofire` is no
66-
longer updated and has been replaced by the separate Android and Java
67-
artifacts as described below.
64+
In order to use GeoFire in your project, you need to [add the Firebase Admin
65+
SDK](https://firebase.google.com/docs/admin/setup). After that you can include GeoFire with one of the choices below.
6866

6967
### Gradle
7068

71-
Add a dependency for GeoFire to your `gradle.build` file.
72-
73-
For Android applications:
74-
75-
```groovy
76-
dependencies {
77-
compile 'com.firebase:geofire-android:2.3.1'
78-
}
79-
```
80-
81-
For non-Android Java applications:
69+
Add a dependency for GeoFire to your `build.gradle` file:
8270

8371
```groovy
8472
dependencies {
@@ -89,19 +77,7 @@ dependencies {
8977

9078
### Maven
9179

92-
GeoFire also works with Maven.
93-
94-
For Android applications:
95-
96-
```xml
97-
<dependency>
98-
<groupId>com.firebase</groupId>
99-
<artifactId>geofire-android</artifactId>
100-
<version>2.3.1</version>
101-
</dependency>
102-
```
103-
104-
For non-Android Java applications:
80+
Add a dependency for GeoFire to your `pom.xml` file:
10581

10682
```xml
10783
<dependency>
@@ -111,22 +87,7 @@ For non-Android Java applications:
11187
</dependency>
11288
```
11389

114-
### Jar-File
115-
116-
You can also download the jar file from the latest release on the [releases
117-
page](https://github.com/firebase/geofire-java/releases).
118-
119-
120-
## Getting Started with Firebase
121-
122-
GeoFire requires the Firebase database in order to store location data. You can [sign up here for a free
123-
account](https://console.firebase.google.com/).
124-
125-
126-
## Quickstart
127-
128-
This is a quickstart on how to use GeoFire's core features. There is also a
129-
[full API reference available online](https://geofire-java.firebaseapp.com/docs/).
90+
## Usage
13091

13192
### GeoFire
13293

@@ -338,24 +299,10 @@ the query to the new visible map area after a user scrolls.
338299

339300

340301
## Deployment
302+
341303
- In your local environment set `$BINTRAY_USER` and `$BINTRAY_KEY` to your
342304
Bintray.com username and API key.
343305
- Checkout and update the master branch.
344306
- Run `./release.sh` to build and deploy.
345307
- On bintray.com, publish the draft artifacts.
346-
- Update [firebase-versions](https://github.com/firebase/firebase-clients/blob/master/versions/firebase-versions.json) with the changelog from this version
347-
- tweet the release
348-
349-
## API Reference
350-
351-
[A full API reference is available here](https://geofire-java.firebaseapp.com/docs/).
352-
353-
354-
## Contributing
355-
356-
If you want to contribute to GeoFire for Java, clone the repository
357-
and just start making pull requests.
358-
359-
```bash
360-
git clone https://github.com/firebase/geofire-java.git
361308
```

0 commit comments

Comments
 (0)