From 47d65429dca185acfed8a620e65eba82acf2bdbd Mon Sep 17 00:00:00 2001 From: Bradlee Speice Date: Sat, 3 May 2014 11:37:22 -0400 Subject: [PATCH] And fix the post url tag --- _posts/2014-05-01-android-studio-now-in-business.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2014-05-01-android-studio-now-in-business.md b/_posts/2014-05-01-android-studio-now-in-business.md index 7cb8759..8d167f6 100644 --- a/_posts/2014-05-01-android-studio-now-in-business.md +++ b/_posts/2014-05-01-android-studio-now-in-business.md @@ -22,7 +22,7 @@ Problem: **Configuring builds to use Gradle.** So my build of JSword was going just fine, but I wanted to have a one-click build of the entire MinimalBible app (and eventually use something like [Travis](https://travis-ci.org/)). That means getting a build of JSword working alongside the main build. -Originally, it would have made the most sense to stick with Ant builds and re-use targets from that. But me being adventurous and wanting to try the new shiny tooling, I gave Gradle a shot. The results really didn't [pan out]({% post 2014-04-22-xml-is-a-terrible-programming-language.md %}). +Originally, it would have made the most sense to stick with Ant builds and re-use targets from that. But me being adventurous and wanting to try the new shiny tooling, I gave Gradle a shot. The results really didn't [pan out]({% post_url 2014-04-22-xml-is-a-terrible-programming-language %}). To be honest, I don't really remember why I gave Android Studio a second shot. But I did, and got a [preliminary build](https://github.com/MinimalBible/MinimalBible/commit/77c797d4f1621511f659557397f597fd0843a6f6) working after an hour or two. I knew the build wasn't perfect, but developing in Android Studio was now a live option.