Permalink
Browse files

Step 2: Import jars for Gradle dependencies

I got these by running "./gradlew --debug assembleDebug", grabbing the
jars using during javac, and copying them into the repo.  For the aar, I
got the original (unexploded) aar from the support repository.

None of the dependencies in build.gradle are provided scope, so I think
it's okay for us to just include these as normal dependencies.
  • Loading branch information...
dreiss committed Jul 8, 2014
1 parent c2080b1 commit 6c809273e70428f2f465cdeef568e1f35c30b439
View
@@ -38,7 +38,6 @@ description
# other
*.odg#
proguard
libs
*.DS_Store
src/de/danoeh/antennapod/util/flattr/FlattrConfig.java
gradle.properties
Binary file not shown.
View
Binary file not shown.
Binary file not shown.
View
Binary file not shown.
View
Binary file not shown.
View
Binary file not shown.

1 comment on commit 6c80927

@kykrueger

This comment has been minimized.

Show comment
Hide comment
@kykrueger

kykrueger Dec 12, 2016

It is quicker to download all project dependencies using a Gradle task.
There is a great stack overflow solution to do so.

The task suggested there is the following added to the build.gradle file responsible for your app.

task copyDependencies(type: Copy) {
   from configurations.compile   
   into 'dependencies'
}

This will download all dependencies into a 'dependencies' folder within your workspace.

kykrueger commented on 6c80927 Dec 12, 2016

It is quicker to download all project dependencies using a Gradle task.
There is a great stack overflow solution to do so.

The task suggested there is the following added to the build.gradle file responsible for your app.

task copyDependencies(type: Copy) {
   from configurations.compile   
   into 'dependencies'
}

This will download all dependencies into a 'dependencies' folder within your workspace.

Please sign in to comment.