Community
Participate
Working Groups
comment #6 in bug 30771 highlights the need for better control over when an extrernal tool builder runs. On the one hand people do not want their ant scripts running on ever incremental build but on the other, there are cases where either a full build is too much work or hard to remember. Yet if neither case is acceptable to the user, in what situation would they use an external tool builder? Perhaps some middle ground could be had by allowing for the more detailed specification of changes that should trigger the builder. For example, if you could spec that the builder should only be run if there are resource changes in a particular folder or a particular kind of file (e.g. *.java). This would solve the case discussed in bug 30771. This is not something for 2.1 as we are very late in the cycle but could be considered for 2.2.
This is very close to bug 25337. Deferred for post 2.1
*** Bug 31511 has been marked as a duplicate of this bug. ***
Reopening...
Proto-typing adding working set support to the external builder
*** This bug has been marked as a duplicate of 25337 ***