Databases
StackOverflow2013
Postsdbo
POMy android project is "using an old version of the Android Gradle plug-in"
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMy android project is "using an old version of the Android Gradle plug-in"
    primarykey
    data
    text
    <p>I am getting this error </p> <pre><code>Project is using an old version of the Android Gradle plug-in. The minimum supported version is 0.6.3. Please update the version of the dependency 'com.android.tools.build:gradle' in your build.gradle files. </code></pre> <p>So i did research and realized I had to go to my project build.gradle file and change this part of my dependencies</p> <pre><code>dependencies { classpath 'com.android.tools.build:gradle:0.4' } </code></pre> <p>but my build.gradle file doesnt have that. This is my build.gradle file</p> <pre><code>apply plugin: 'android' dependencies { compile fileTree(dir: 'libs', include: '*.jar') compile project(':Desktop:Coding:SlidingMenu-master:library') } android { compileSdkVersion 19 buildToolsVersion "19.0.0" sourceSets { main { manifest.srcFile 'AndroidManifest.xml' java.srcDirs = ['src'] resources.srcDirs = ['src'] aidl.srcDirs = ['src'] renderscript.srcDirs = ['src'] res.srcDirs = ['res'] assets.srcDirs = ['assets'] } // Move the tests to tests/java, tests/res, etc... instrumentTest.setRoot('tests') // Move the build types to build-types/&lt;type&gt; // For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ... // This moves them out of them default location under src/&lt;type&gt;/... which would // conflict with src/ being used by the main source set. // Adding new build types or product flavors should be accompanied // by a similar customization. debug.setRoot('build-types/debug') release.setRoot('build-types/release') } } </code></pre> <p>What am I missing?</p> <p>EDIT:</p> <p>updated code</p> <pre><code> apply plugin: 'android' buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:0.6.4' compile fileTree(dir: 'libs', include: '*.jar') compile project(':Desktop:Coding:SlidingMenu-master:library') } } android { compileSdkVersion 19 buildToolsVersion "19.0.0" sourceSets { main { manifest.srcFile 'AndroidManifest.xml' java.srcDirs = ['src'] resources.srcDirs = ['src'] aidl.srcDirs = ['src'] renderscript.srcDirs = ['src'] res.srcDirs = ['res'] assets.srcDirs = ['assets'] } // Move the tests to tests/java, tests/res, etc... instrumentTest.setRoot('tests') // Move the build types to build-types/&lt;type&gt; // For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ... // This moves them out of them default location under src/&lt;type&gt;/... which would // conflict with src/ being used by the main source set. // Adding new build types or product flavors should be accompanied // by a similar customization. debug.setRoot('build-types/debug') release.setRoot('build-types/release') } } </code></pre> <p>new error</p> <pre><code> No signature of method: org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.compile() is applicable for argument types: (org.gradle.api.internal.file.collections.DefaultConfigurableFileTree) values: [directory 'libs'] Possible solutions: module(java.lang.Object) &lt;a href="error in file: C:\Users\cmtc\Documents\Android\StayHealthy\build.gradle at line: 10"&gt;Build file 'C:\Users\cmtc\Documents\Android\StayHealthy\build.gradle' line: 10 </code></pre> <p></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCam Connor
    1. USCam Connor
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload