From 7def118e3151ffaab614e825353427384f6adb8a Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Mon, 23 Aug 2021 07:37:04 -0700 Subject: [PATCH] Fix links to Maven artifacts. Fixes #250. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7059c61..a4315df 100644 --- a/README.md +++ b/README.md @@ -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 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 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 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.