Problem with Proguard and XmlPullParser?

Your ProGuard configuration and build process seem to be mixing up program jars and library jars For ProGuard, you can probably specify all the listed jars as input jars (with -injars). Their processed versions will end up in the output jar (-outjars) You can indeed avoid warnings about duplicate xmlpull classes by filtering them out of android.jar. ProGuard will also print out warnings should there be any duplicates in the input jars.

You can then filter out those duplicates as well You should not specify java. Home>/lib/rt. Jar as a library jar, since this jar is not present as a library on Android devices either.

Some of the listed jars depend on it though, so at least parts of them are not entirely compatible with the Android runtime. The cleanest solution to avoid warnings about offending classes is to filter them out of the corresponding input jars (e.g. A filter! Com/thoughtworks/xstream/converters/extended/ColorConverter.

Class ). Alternatively, you can bluntly switch off these warnings (e. G dontwarn com.thoughtworks.xstream.converters.extended.

ColorConverter ) For the Dalvik compiler, you should only specify the processed output jar, not any of the program jars that went into it. Otherwise, you will get duplicate classes: some unprocessed copies and some partly obfuscated copies. They don't blend and lead to Error1 and NoSuchMethodErrors.

Your ProGuard configuration and build process seem to be mixing up program jars and library jars. For ProGuard, you can probably specify all the listed jars as input jars (with -injars). Their processed versions will end up in the output jar (-outjars).

You can indeed avoid warnings about duplicate xmlpull classes by filtering them out of android.jar. ProGuard will also print out warnings should there be any duplicates in the input jars. You can then filter out those duplicates as well.

You should not specify /lib/rt. Jar as a library jar, since this jar is not present as a library on Android devices either. Some of the listed jars depend on it though, so at least parts of them are not entirely compatible with the Android runtime.

The cleanest solution to avoid warnings about offending classes is to filter them out of the corresponding input jars (e.g. A filter! Com/thoughtworks/xstream/converters/extended/ColorConverter. Class).

Alternatively, you can bluntly switch off these warnings (e.g. -dontwarn com.thoughtworks.xstream.converters.extended. ColorConverter). For the Dalvik compiler, you should only specify the processed output jar, not any of the program jars that went into it.

Otherwise, you will get duplicate classes: some unprocessed copies and some partly obfuscated copies. They don't blend and lead to Error1 and NoSuchMethodErrors.

To let library classes take precedence and shut up Proguard, put this in main-rules. Xml (but copy a part to build. Xml first): -libraryjars ${android.

Libraryjars}(!org/xmlpull/v1/XmlPullParser. Class,! Org/xmlpull/v1/XmlPullParserException.

Class) You'll run into other problems with XStream as well, see: Proguard and XStream with omitField() on Android For the whole story: https://plus.google. Com/112617873637231221858/posts/YxWrEJRMSo4.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.