Manually installing just hits another missing artifact:
Caused by:
org.gradle.api.internal.artifacts.ivyservice.ModuleVersionNotFoundException:
Could not find org.eclipse.jdt.core.compiler:ecj:4.2.2.
Searched in the following locations:
file:/Volumes/aosp-tools/out/repo/org/eclipse/jdt/core/compiler/ecj/4.2.2/ecj-4.2.2.pom
file:/Volumes/aosp-tools/out/repo/org/eclipse/jdt/core/compiler/ecj/4.2.2/ecj-4.2.2.jar
Is there something prior to gw clean buildTest?
On Thu, Jul 17, 2014 at 9:48 AM, Jake Wharton <[email protected]> wrote:
> ProGuard 4.11 isn't being installed into the repo.
>
>
> Caused by:
> org.gradle.api.internal.artifacts.ivyservice.ModuleVersionNotFoundException:
> Could not find net.sf.proguard:proguard-gradle:4.11.
> Searched in the following locations:
>
> file:/Volumes/aosp-tools/out/repo/net/sf/proguard/proguard-gradle/4.11/proguard-gradle-4.11.pom
>
> file:/Volumes/aosp-tools/out/repo/net/sf/proguard/proguard-gradle/4.11/proguard-gradle-4.11.jar
>
>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
