AfflictionNetworks/getdown
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix links to Maven artifacts.

Browse Source 
Fixes #250.
This commit is contained in:
Michael Bayne
2021-08-23 07:37:04 -07:00
parent cdecfde5f1
commit 7def118e31
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -56,11 +56,11 @@ Getdown will likely need to be integrated into your build. We have separate inst
Getdown is comprised of three Maven artifacts (jar files), though you probably only need the first Getdown is comprised of three Maven artifacts (jar files), though you probably only need the first
one: one:
* [getdown-launcher](http://repo2.maven.org/maven2/com/threerings/getdown/getdown-launcher) * [getdown-launcher](https://repo1.maven.org/maven2/com/threerings/getdown/getdown-launcher)
contains minified (via Proguard) code that you actually run to update and launch your app. It contains minified (via Proguard) code that you actually run to update and launch your app. It
also contains the tools needed to build a Getdown app distribution. also contains the tools needed to build a Getdown app distribution.
* [getdown-core](http://repo2.maven.org/maven2/com/threerings/getdown/getdown-core) contains the * [getdown-core](https://repo1.maven.org/maven2/com/threerings/getdown/getdown-core) contains the
core logic for downloading, verifying, patching and launching an app as well as the core logic core logic for downloading, verifying, patching and launching an app as well as the core logic
for creating an app distribution. It does not contain any user interface code. You would only for creating an app distribution. It does not contain any user interface code. You would only
use this artifact if you were planning to integrate Getdown directly into your app. use this artifact if you were planning to integrate Getdown directly into your app.