Does not work because of javax.annotations.Nonnull in dependent JAR about parceler

[johncarl81]

Done. This will show up in the upcoming bug fix release, probably this weekend.

You are referring to javax.annotation.Nullable correct, the same issue as in johncarl81/transfuse#52 ?

[johncarl81]

One thought... is your android build including the Parceler (not Parceler-api) jar contents and dependencies into your final apk?

[thubalek]

I'm using Gradle and it possible that Parceler is added into APK. But it is
later removed by proguard, I guess.

---

Sent from my Nexus 5. Excuse my brevity.
Check my apps at http://android.hubalek.net and at
http://blackberry.hubalek.net
Dne 6. 1. 2014 20:09 "John Ericksen" [email protected] napsal(a):

One thought... is your android build including the Parceler (not
Parceler-api) jar contents and dependencies into your final apk?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-31676643
.

[johncarl81]

I'd recommend using android-apt plugin to run Parceler during the annotation processing phase and ignore it and its dependencies for the final apk, like the following:

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.1'
        classpath 'com.android.tools.build:gradle:0.6.+'
    }
}
apply plugin: 'android'
apply plugin: 'android-apt'

repositories {
    mavenCentral()
}

dependencies {
    apt 'org.parceler:parceler:0.2.3'
    compile 'org.parceler:parceler-api:0.2.3'
}

android {
    compileSdkVersion 19
    buildToolsVersion "19.0.0"

    defaultConfig {
        minSdkVersion 7
        targetSdkVersion 19
    }

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_6
        targetCompatibility JavaVersion.VERSION_1_6
    }
}

This avoids the need to even worry about Proguard and will hopefully solve your duplicate class problem outright. Let me know if this works for you.

[thubalek]

Will look at it tomorrow, thanks for suggestion, I really appreciate it.

BTW: I'm curious why you can't move javax.* classes out of the jar? I'm
using multiple annotation processors (Dagger, Butter Knife) and all work
without any extra plugin.

---

Sent from my Nexus 5. Excuse my brevity.
Check my apps at http://android.hubalek.net and at
http://blackberry.hubalek.net
Dne 6. 1. 2014 20:31 "John Ericksen" [email protected] napsal(a):

I'd recommend using android-apt plugin to run Parceler during the
annotation processing phase and ignore it and its dependencies for the
final apk, like the following:

buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'com.neenbedankt.gradle.plugins:android-apt:1.1'
classpath 'com.android.tools.build:gradle:0.6.+'
}
}
apply plugin: 'android'
apply plugin: 'android-apt'

repositories {
mavenCentral()
}

dependencies {
apt 'org.parceler:parceler:0.2.3'
compile 'org.parceler:parceler-api:0.2.3'
}

android {
compileSdkVersion 19
buildToolsVersion "19.0.0"

defaultConfig {
    minSdkVersion 7
    targetSdkVersion 19
}

compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_6
    targetCompatibility JavaVersion.VERSION_1_6
}

}

This avoids the need to even worry about Proguard and will hopefully solve
your duplicate class problem outright. Let me know if this works for you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-31678741
.

[johncarl81]

I believe that I can move the javax.* classes out of the transfuse-bootstrap jar and rely on jsr305 instead.. if that's necessary. I ran into a couple stumbling blocks this weekend regarding the removal of javax.annotation.Nullable, but I should have it fixed soon. I'll let you know.

[johncarl81]

This is incorporated into the 0.2.5 release