Community
Participate
Working Groups
Build 20020813 I missed to set an attribute in my ant file and got warned with a dialog (ok). In addition the following entry was written to the DOS console: [Fatal Error] :14:15: Element type "isset" must be followed by either attribute specifications, ">" or "/>". I guess this is the ant output (and for ant it might be a fatal error) however it is misleading for an Eclipse user to see a fatal error in the Eclipse console. It would be nice if it would be at least prefixed with ant: ant: [Fatal Error] :14:15: Element type "isset" must be follow....
On the latest (released to the Oct 1 integration build), I cannot reproduce the problem.
Please verify (Jared)
Daniel, can you provide a script (the smaller, the better) which demonstrates the problem you had? Can you still reproduce this problem on the latest build?
Attached a file causing the problem.
Created attachment 2106 [details] bad ant script
The attached script works. Now introduce an error - e.g. remove the '>' of the closing target tag. This makes line 5 look like ==> </target
Thanks. I also cannot reproduce the problem on the new code.
Verified.
What do you mean with "new code"? Testing against 20021001 still shows me the error. If you did not test with newer code (which changed in that area) then you should see the error. Here are the steps again: 1. add attached file to workspace 2. remove the '>' of the closing target tag. This makes line 5 look like ==> </target 3. run ant on the file ==> Error appears in *console* where where I started Eclipse (not in the .log): [Fatal Error] :7:2: The end-tag for element type "target" must end with a '>' delimiter.
New work in the external tools UI for the past month or so has taken place in a side branch. It should be noted that I've just started working on the UI and had nothing to do with this. ;) We just moved the code from this branch into the HEAD branch on Friday and we don't know when we'll start submitting it to builds (we inherited a mess). To test on the new code, you'd need to check the org.eclipse.ui.externaltools project out of the HEAD branch.
Ok. I just wanted to make sure that the console has been checked for the error to appear and not the .log.