Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 GTB5 Build Identifier: 20090621-0832 <eclipse.incrementalBuild/> can be used to build a project. But there are several things that most build-related Ant tasks (such as <javac/>) do but <eclipse.incrementalBuild/> does not: 1. They typically log build errors and warnings. 2. They typically "fail" the build if any compilation errors occurred (unless failonerror="false"). 3. <javac/> also has a fairly recent addition, errorProperty="propertyname", which lets you specify a property that will be set to "true" if any build errors occurred. The first and second are especially unusual. Basically, <eclipse.incrementalBuild/> silently "succeeds" no matter what actually happened during the build. This patch addresses these problems: 1. Adds a "showproblems" attribute which defaults to true. If true, errors and warnings are logged. 2. Adds a "failonerror" attribute which defaults to true. If true, and the specified resources have any build errors, then an exception is thrown indicating that the Ant task failed. 3. Adds an "errorProperty" attribute. Frustratingly, I was unable to test this patch -- it built, but I was unable to configure my environment to create a working Eclipse environment in which to test these changes. Not sure what I was doing wrong. Reproducible: Always
Created attachment 148695 [details] Proposed patch
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.
