build imsdroid via eclipse

```
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response

What steps will reproduce the problem?
1. use adt-bundle-windows-x86-20140321 to build imsdroid
2. export signed application package to generate package, then report errors as
shown below:

error 1

Obsolete ProGuard file; use -keepclasseswithmembers instead of
-keepclasseswithmembernames

Issue: Looks for problems in proguard config files
Id: Proguard

Using -keepclasseswithmembernames in a proguard config file is not correct; it
can cause some symbols to be renamed which should not be.
Earlier versions of ADT used to create proguard.cfg files with the wrong
format. Instead of -keepclasseswithmembernames use -keepclasseswithmembers,
since the old flags also implies "allow shrinking" which means symbols only
referred to from XML and not Java (such as possibly CustomViews) can get
deleted.

[http://http://code.google.com/p/android/issues/detail?id=16384]

error 2
The id "sview_call_trying_imageView_avatar" is not defined anywhere. Did you
mean view_call_trying_imageView_avatar ?

Issue: Checks for id references in RelativeLayouts that are not defined
elsewhere
Id: UnknownId

The @+id/ syntax refers to an existing id, or creates a new one if it has not
already been defined elsewhere. However, this means that if you have a typo in
your reference, or if the referred view no longer exists, you do not get a
warning since the id will be created on demand. This check catches errors where
you have renamed an id without updating all of the references to it.

error 3
"app_name" is not translated in fr, it

Issue: Checks for incomplete translations where not all strings are translated
Id: MissingTranslation

If an application has more than one locale, then all the strings declared in
one language should also be translated in all other languages.

If the string should not be translated, you can add the attribute
translatable="false" on the element, or you can define all your
non-translatable strings in a resource file called donottranslate.xml. Or, you
can ignore the issue with a tools:ignore="MissingTranslation" attribute.

By default this detector allows regions of a language to just provide a subset
of the strings and fall back to the standard language strings. You can require
all regions to provide a full translation by setting the environment variable
ANDROID_LINT_COMPLETE_REGIONS.

You can tell lint (and other tools) which language is the default language in
your res/values/ folder by specifying tools:locale="languageCode" for the root
element in your resource file. (The tools prefix refers to the
namespace declaration http://schemas.android.com/tools.)

error 4
@+id/screen_contacts_radioButton_local is not a sibling in the same
RelativeLayout

Issue: Checks for id references in RelativeLayouts that are not referencing a
sibling
Id: NotSibling

Layout constraints in a given RelativeLayout should reference other views
within the same relative layout.

error 5
"stringarray_codes" is translated here but not found in default locale

Issue: Checks for translations that appear to be unused (no default language
string)
Id: ExtraTranslation

If a string appears in a specific language translation file, but there is no
corresponding string in the default locale, then this string is probably
unused. (It's technically possible that your application is only intended to
run in a specific locale, but it's still a good idea to provide a fallback.).

Note that these strings can lead to crashes if the string is looked up on any
locale not providing a translation, so it's important to clean them up.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
imsdroid rev 569
windows 7

Please provide any additional information below.

```

Original issue reported on code.google.com by `andrewm...@gmail.com` on 30 Jun 2014 at 8:30

Start by reproducing the signed-package build with the specified ADT bundle on Windows 7, then inspect the ProGuard configuration files and the Android resource files implicated by the lint errors. Done means the listed ProGuard and resource-reference, translation, and RelativeLayout errors are resolved and the signed application package builds successfully.

Written by the indexing model from the issue text.