https://github.com/schnatterer/nusic
your new music (android app)
https://github.com/schnatterer/nusic
android fdroid gradle music musicbrainz
Last synced: over 1 year ago
JSON representation
your new music (android app)
- Host: GitHub
- URL: https://github.com/schnatterer/nusic
- Owner: schnatterer
- License: gpl-3.0
- Created: 2013-09-01T12:04:27.000Z (almost 13 years ago)
- Default Branch: main
- Last Pushed: 2022-01-03T13:16:10.000Z (over 4 years ago)
- Last Synced: 2025-03-17T23:05:14.603Z (over 1 year ago)
- Topics: android, fdroid, gradle, music, musicbrainz
- Language: Java
- Size: 8.72 MB
- Stars: 42
- Watchers: 5
- Forks: 7
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.txt
Awesome Lists containing this project
README
nusic - your new music
=====
Never again miss a new album release of your favorite artists - always stay informed by nusic.
nusic uses [MusicBrainz](http://musicbrainz.org/) - the free music encyclopedia - to find out about new releases of the artists on your phone.
No account necessary.
## Download
You can download the latest version as APK from [GitHub](https://github.com/schnatterer/nusic/releases/latest) or get the app directly from [F-Droid](https://f-droid.org/app/info.schnatterer.nusic).
Due to Google's policy newer version can no longer be supplied via [Google Play](https://play.google.com/store/apps/details?id=info.schnatterer.nusic). However, the APKs found on GitHub are compatible, so you can use those to upgrade your old installations from Google Play.
[
](https://f-droid.org/app/info.schnatterer.nusic)
[
](https://play.google.com/store/apps/details?id=info.schnatterer.nusic)
## Licenses
Copyright © 2013 Johannes Schnatterer.
Licensed under the GNU General Public License Version 3.
See the [License](LICENSE.txt) and the [licenses of dependencies](NOTICE.md).
## Release notes
See [Changelog](CHANGELOG.md) and [Releases](https://github.com/schnatterer/nusic/releases).
## Permissions
What kind of permission does nusic require and why does it require them?
- Network communication, full network access: Check MusicBrainz for new releases
- Nework communication, view network connections: Get notified about available connection to the internet in order to start checking for new releases.
- Yor applications information, run at startup: Schedule regular checking for new releases via the Android alarm manager
- System tools, test access to protected storage: Get the artists that are stored on the device
- Affects Battery, prevent phone from sleeping: Prevent the device from falling back to sleep while searching for new releases
## Build
### Modules
| Module | Packaging | Description |
| ------------- | ------------- | ------------- |
| parent | - | Global build properties for all modules |
| nusic-apk | apk | Assembly maven module containing the guice module, wires up all dependencies and builds the APK |
| nusic-ui-android | aar | Contains all android specific frontend-code |
| nusic-core-api | jar | Interfaces of the central logic module |
| nusic-core-android | jar | Android-specific implementation of the central logic module |
| nusic-data-api | jar | Interfaces of the persistence module |
| nusic-data-android | jar | Android-specific implementation of the persistence module |
| nusic-domain | jar | Domain objects for persistence and migration between the layers |
| nusic-util | jar | Utility module, containing logic common to all modules |
### Gradle
In order to build the APK use the [SDK manager](https://developer.android.com/tools/help/sdk-manager.html) to download the SDK Version specified in the [parent project's build.gradle](build.gradle) and deploy android to your local maven repo using [maven-android-sdk-deployer](https://github.com/mosabua/maven-android-sdk-deployer). Also make sure to set your `ANDROID_HOME` environment variable to `sdk` folder of your Android SDK.
Then just run
```sh
gradlew clean check assembleDebug
```
to compile from scratch, run the tests and create a debug-signed APK, or run
```sh
gradlew clean check assembleRelease
```
to create a signed APK, using an custom keystore.
For passing the credentials for this keystore via the command line there are four options
1. Define them in your `~/.gradle/gradle.properties` like so
```ini
signKeystore=FULL/path/to/keystore
signAlias=the key's alias within the keystore
signKeypass=password for keystore
signStorepasss=password for key
```
2. Pass them as command line properties, e.g.
```sh
gradlew clean check assembleRelease -PsignAlias="the key's alias within the keystore"
```
3. Pass them as environment variables, e.g.
```sh
export ORG_GRADLE_PROJECT_signAlias=the key's alias within the keystore
```
4. or pass them as system property, e.g.
```sh
gradlew clean connectedCheck assembleRelease -Dorg.gradle.project.signKeystore=signAlias="the key's alias within the keystore"
```
## Creating a release
1.Set Version
```sh
gradlew setVersion -PnewVersion=2.1.1
```
2. Update [changelog](CHANGELOG.md)
3. Commit
```sh
git add .
git commit -m "Prepare release v.2.1.1"
```
4. Finish release: Tag
```sh
git tag -s "v.2.1.1" -m "v.2.1.1"
```
5. Set next dev version & commit
```sh
gradlew setVersion -PnewVersion=2.1.2-SNAPSHOT
git add .
git commit -m "Prepare for next development iteration v.2.1.2-SNAPSHOT"
```
6. Checkout and build tag
```sh
git checkout tags/v.2.1.1
gradlew clean connectedCheck assembleRelease
```
7. Push all branches & tags
```sh
git push --all
git push --tags
```
8. Upload artifact: [Github](https://github.com/schnatterer/nusic/releases)
9. Add changelog to github release page: https://github.com/schnatterer/nusic/releases/tag/v.2.1.1