I tried Add Files option to my code and I added the "android" file from SDK. When I compile it does clear the "No library found" error message (great!) but the Build fails and for the following reason. Can you suggest what to do here?

Using Processing 0192 and my SDK is current i.e. API 9.

ant debug:
------

-dex:
     [echo] Converting compiled files and external libraries into C:\Desktop\Android\FlakeFrenzy\android\bin\classes.dex...
    [apply]
    [apply] trouble processing "javax/net/SocketFactory.class":
    [apply]
    [apply] Ill-advised or mistaken usage of a core class (java.* or javax.*)
    [apply] when not building a core library.
    [apply]
    [apply] This is often due to inadvertently including a core library file
    [apply] in your application's project, when using an IDE (such as
    [apply] Eclipse). If you are sure you're not intentionally defining a
    [apply] core class, then this is the most likely explanation of what's
    [apply] going on.
    [apply]
    [apply] However, you might actually be trying to define a class in a core
    [apply] namespace, the source of which you may have taken, for example,
    [apply] from a non-Android virtual machine project. This will most
    [apply] assuredly not work. At a minimum, it jeopardizes the
    [apply] compatibility of your app with future versions of the platform.
    [apply] It is also often of questionable legality.
    [apply]
    [apply] If you really intend to build a core library -- which is only
    [apply] appropriate as part of creating a full virtual machine
    [apply] distribution, as opposed to compiling an application -- then use
    [apply] the "--core-library" option to suppress this error message.
    [apply]
    [apply] If you go ahead and use "--core-library" but are in fact
    [apply] building an application, then be forewarned that your application
    [apply] will still fail to build or run, at some point. Please be
    [apply] prepared for angry customers who find, for example, that your
    [apply] application ceases to function once they upgrade their operating
    [apply] system. You will be to blame for this problem.
    [apply]
    [apply] If you are legitimately using some code that happens to be in a
    [apply] core package, then the easiest safe alternative you have is to
    [apply] repackage that code. That is, move the classes in question into
    [apply] your own package namespace. This means that they will never be in
    [apply] conflict with core system classes. JarJar is a tool that may help
    [apply] you in this endeavor. If you find that you cannot do this, then
    [apply] that is an indication that the path you are on will ultimately
    [apply] lead to pain, suffering, grief, and lamentation.
    [apply]
    [apply] 1 error; aborting

BUILD FAILED
C:\android-sdk-windows\tools\ant\main_rules.xml:449: The following error occurred while executing this line:
C:\android-sdk-windows\tools\ant\main_rules.xml:199: apply returned: 1