![apache ant build errors apache ant build errors](https://www.provartesting.com/wp-content/uploads/2020/09/img_599455aa7d006-3.png)
![apache ant build errors apache ant build errors](https://i.stack.imgur.com/XEY4i.png)
Looks like this is already implemented, but in a wrong way.Ĭompile errors should be represented as markers, not as log entries like this:īootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_USĬommand-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\e\w\master -clean -consolelog -showlocation -console -debug C:\e\w\debug-options.properties Deleting: C:\e\w\master\git\\.ui\snippetsupport.jarĬ:\e\w\master\git\\.ui\scripts\buildExtraJAR.xml:50: Unable to delete file C:\e\w\master\git\\.ui\snippetsupport.jar The failure was not obvious to me, since it was only visible in the console for that build, but not as an error marker on the build file.īuildfile: C:\e\w\master\git\\.ui\scripts\buildExtraJAR.xml Since that locked the /.ui/snippetsupport.jar file, the Ant builder that is configured on that project failed. When implementing bug 463236, it happened to me that a snippet evaluation was still running in a runtime Eclipse. When an Ant builder fails, the Eclipse Ant plug-in should create a problem marker on the Ant build file and include the error message.