Re: Xcode 3.2 fails to highlight errors in Java source
Re: Xcode 3.2 fails to highlight errors in Java source
- Subject: Re: Xcode 3.2 fails to highlight errors in Java source
- From: "Pelaia II, Tom" <email@hidden>
- Date: Wed, 02 Sep 2009 13:06:32 -0400
- Acceptlanguage: en-US
- Thread-topic: Xcode 3.2 fails to highlight errors in Java source
Hi
I just installed Snow Leopard and Xcode 3.2 and reproduced the problem
you posted. I have discovered that the cause of the problem is dues to
the Ant output. The output for the error message is missing an
"error:" text after the file specification and line number. I tested
this by generating Ant output using the echo task and it correctly
identified the error and was able to jump to the appropriate line
number.
Unfortunately, I haven't yet developed a workaround, but it may be
possible by using a "sed" to process the output of Ant.
best regards,
tom
>
> I see that Xcode 3.2 does not correctly highlight errors in Java
> source code. Warnings are correctly parsed and highlighted within
> the Java source, but errors are only reported in the build results
> window. That is to say, there is nothing that ties the errors
> presented with the build results to the Java source file in the
> Xcode project. When using Xcode 3.2, you must observe that you had
> an error, and then try your best to determine where in the original
> source file the affected line is. It really is quite cumbersome.
>
> I mentioned this to the engineers in the Xcode lab during this
> year's WWDC, but it seems that the version of Xcode that shipped
> with Snow Leopard retains this problem. I submitted this problem
> back in June as bug #6965152.
>
> I'd love to know if there is a work around for this.
>
> =========================
> Michael F. Ellis
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden