Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 509461

Summary:	Ant builder should create problem marker when javac/ecj build fails
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	Ant	Assignee:	Platform-Ant-Inbox <platform-ant-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	noopur_gupta
Version:	4.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:	133184
Bug Blocks:

Description Markus Keller

2016-12-19 10:57:30 EST

Via http://stackoverflow.com/questions/29237709/detect-error-in-eclipse-ant-builder#comment48336323_29237709 , I learned that enabling

  Preferences > Ant > Create problem markers from "javac" results

already implements this for problems reported by javac or ecj (IAntUIPreferenceConstants#ANT_CREATE_MARKERS from bug 133184).

I think this preference should be enabled by default.


Bug 463714 is a related request (also turn a failed Ant build into an error marker).

Comment 1 Markus Keller

2016-12-19 11:10:05 EST

For a real use case, modify e.g. JDT UI's JarRsrcLoader or the source of one of JDT Debug's helper libraries.

Comment 2 Markus Keller

2016-12-19 11:12:45 EST

Bummer, the feature should not be enabled by default at this time.
It first needs to be fixed. I'm now getting tons of exceptions in the log:

eclipse.buildId=4.7.0.I20161219-0145
java.version=1.8.0_102
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -showlocation
Command-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

org.eclipse.ant.launching
Error
Mon Dec 19 16:39:38 CET 2016
Failure of Background Ant Build

org.eclipse.core.runtime.CoreException: C:\e\w\master\git\eclipse.jdt.ui\org.eclipse.jdt.ui\scripts\build_jar-in-jar-loader.xml:22: Compile failed; see the compiler error output for details.
	at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
	at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
	at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:270)
	at java.lang.Thread.run(Thread.java:745)
Caused by: C:\e\w\master\git\eclipse.jdt.ui\org.eclipse.jdt.ui\scripts\build_jar-in-jar-loader.xml:22: Compile failed; see the compiler error output for details.
	at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1181)
	at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:936)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.Target.execute(Target.java:435)
	at org.apache.tools.ant.Target.performTasks(Target.java:456)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1260)
	at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:711)
	at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:531)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
	... 2 more

org.eclipse.ui.console
Error
Mon Dec 19 16:43:27 CET 2016
Problems occurred when invoking code from plug-in: "org.eclipse.ui.console".

java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
	at java.util.ArrayList$Itr.next(ArrayList.java:851)
	at org.eclipse.ant.internal.ui.console.AbstractJavacPatternMatcher.consoleClosed(AbstractJavacPatternMatcher.java:159)
	at org.eclipse.ant.internal.ui.console.TaskLineTracker.consoleClosed(TaskLineTracker.java:64)
	at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.consoleClosed(ConsoleLineNotifier.java:90)
	at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.propertyChange(ConsoleLineNotifier.java:141)
	at org.eclipse.ui.console.AbstractConsole$PropertyNotifier.run(AbstractConsole.java:96)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.console.AbstractConsole$PropertyNotifier.notify(AbstractConsole.java:111)
	at org.eclipse.ui.console.AbstractConsole.firePropertyChange(AbstractConsole.java:229)
	at org.eclipse.ui.console.TextConsole.checkFinished(TextConsole.java:495)
	at org.eclipse.ui.console.TextConsole.matcherFinished(TextConsole.java:486)
	at org.eclipse.ui.internal.console.ConsolePatternMatcher$MatchJob.run(ConsolePatternMatcher.java:167)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

Comment 3 Markus Keller

2016-12-19 11:25:58 EST

(In reply to Markus Keller from comment #2)
The first log entry is bug 463714 comment 2.

The second log entry is the bug in this feature.

Comment 4 Eclipse Genie

2019-10-02 19:39:40 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.