Bug 1546 : Android compiler errors on Windows not reporting actual errors or line number highlighting
Last modified: 2010-06-05 03:51




Status:
ASSIGNED
Resolution:
-
Priority:
P3
Severity:
normal

 

Reporter:
p brouwer
Assigned To:
fry

Attachment Type Created Size Actions
code file application/octet-stream 2010-04-15 07:45 171 bytes
correct behavior, as seen on OS X image/png 2010-04-15 08:03 47.23 KB

Description:   Opened: 2010-04-14 17:29
This is in 0184, but have noticed it on all versions after 0176

Here is a complete transcript of output on console:


Project Target: Google APIs
Vendor: Google Inc.
Platform Version: 2.0.1
API level: 6

BUILD FAILED
D:\android-sdk-windows\platforms\android-6\templates\android_rules.xml:248:
Compile failed; see the compiler error output for details.

Total time: 4 seconds
D:\android-sdk-windows\platforms\android-6\templates\android_rules.xml:248:
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:999)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:820)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at processing.app.tools.android.Build.antBuild(Unknown Source)
at processing.app.tools.android.AndroidTool.runSketchOnDevice(Unknown
Source)
at processing.app.tools.android.AndroidTool.access$500(Unknown Source)
at processing.app.tools.android.AndroidTool$RunHandler.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
Additional Comment #1 From fry 2010-04-14 19:25
You're reporting that errors aren't printed to the console by including the
text of the errors printed to the console? :)

What is it you're looking for, exactly?
Additional Comment #2 From p brouwer 2010-04-14 21:11
I'd like to know what line of code the compiler is complaining about...

back in version 0176, the compiler explained which line of code caused the error.

I realize that eventually, Processing will highlight the line of code, and explain the
error -- but right now I don't see a way to figure out what the compilier is complaining
about, since my code compiles fine in 1.1.

/p



(In reply to comment #1)
>
>
>
> Additional Comment #1 From
>
> fry
> 2010-04-14 19:25
>
> <!--
> addReplyLink(1); //-->[reply]
>
>
>
>
>
>
> You're reporting that errors aren't printed to the console by including the
> text of the errors printed to the console? :)
>
> What is it you're looking for, exactly?
>
>

Additional Comment #3 From fry 2010-04-15 04:20
Can you give me an example that doesn't highlight? This should be working
fine. Many Android errors cannot be parsed, because of the way Google's
tools are set up, but syntax errors, etc should all be ok.
Additional Comment #4 From p brouwer 2010-04-15 07:45
edit]
code file

this demonstrates the compiler not highlighting a program error...
Additional Comment #5 From fry 2010-04-15 08:02
That's unfortunate. It looks like something wrong in the Android tools on
Windows, because it works fine on OS X (and, I suspect, Linux). Not sure if
there's much we can do about it but I'll keep it noted.
Additional Comment #6 From fry 2010-04-15 08:03
edit]
correct behavior, as seen on OS X
This bug is now being tracked here.