My experience on my daily works... helping others ease each other

Sunday, December 28, 2014

merger failed : uses-sdk:minSdkVersion 16 cannot be different than version L declared in library [project_path]\AndroidManifest.xml

After so long design and draw system/solution/software architecture, my programming skill seem rusted. Thought of venturing into programming again as part-time, I started to look into java (still love Netbeans) and Android programming (used Android Studio v1.0.2) for mobile development....And it throw the first challenge to me... can't compiled a sample program. HUH!

First time loading.. got this error:
merger failed : uses-sdk:minSdkVersion 16 cannot be different than version L declared in library [project_path]\app\build\intermediates\exploded-aar\com.android.support\appcompat-v7\21.0.0-rc1\AndroidManifest.xml

Google the issues and found many link.. mostly at StackOverflow ... but it does not helpful at all. After a while googling it, found a solutions that solve my 2 days problem. A simple solutions; change all sdkVersion to "android-L" and compiled it again... and it works... yeeehaaa... here is how it looks like.

before change in file build.gradle
apply plugin: 'com.android.application'

android {
    compileSdkVersion 21
    buildToolsVersion "20.0.0"

    defaultConfig {
        applicationId "com.app.masteramuk.myfirstapp"
        minSdkVersion 16
        targetSdkVersion 21
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.android.support:appcompat-v7:21.+'

after change in file build.gradle
apply plugin: 'com.android.application'

android {
    compileSdkVersion "android-L"
    buildToolsVersion "20.0.0"

    defaultConfig {
        applicationId "com.app.masteramuk.myfirstapp"
        minSdkVersion "android-L"
        targetSdkVersion "android-L"
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])


notes:
  • just change the file build.gradle
  • only apply to code using Android SDK or Android Studio
  • only apply to code that requires to be compatible with lower SDK @ lower Android
Thanks to simple but workable solutions from reddit
Share:

Thursday, December 4, 2014

Network Topology - Leaf-Spine architecture

Leaf-spine is a network topology in which a series of switches form the access layer.
Leaf-spine is an alternate to the three-layer core/aggregation/access network architecture. The leaf switches mesh into the spine, which is a series of several high-throughput layer 3 switches with high port density. Spine switches are essentially the core of the architecture, whereas leaf switches are the access layer that delivers network connection points for servers. Leaf switches also provide uplinks to spine switches.
Every leaf switch connects to every switch in the network fabric; no matter which leaf switch a server is connected to, it has to cross the same number of devices every time it connects to another server. The only exception is when the other server is on the same leaf. Latency is therefore minimized to an acceptable level because each payload only has to travel to a spine switch and another leaf switch to reach its endpoint.
A leaf-spine topology can be layer 2 or layer 3 -- the links between the leaf and spine layer can be switched or routed. In a layer 2 leaf-spine design, Transparent Interconnection of Lots of Links or shortest path bridging takes the place of spanning-tree. All hosts are linked to the fabric and offer a loop-free route to their Ethernet MAC address through a shortest-path-first computation. In a layer 3 design, each link is routed, and it is most efficient when virtual local area networks are sequestered to individual leaf switches or when a network overlay, like VXLAN, is working.

Diagram: Leaf-spine topology



Taken from: TechTarget
Share:

About Me

Somewhere, Selangor, Malaysia
An IT by profession, a beginner in photography

Blog Archive

Blogger templates