Community
Participate
Working Groups
If the working set for an external tool builder is set to a resource in a different project, the external tool builder is not triggered.
Fixed in ExternalToolBuilder BUT (and it is a big BUT), this will only work for the last scoped builder. This is a result of the workaround for bug 39713 (which is a workaround for bug 21029). See these for full details, but basically we can only return the interesting projects for a single builder even thought many builders are building. Darin can you verify that this works in the simple (normal?) case (one scoped builder), and then we will likely have to mark as a readme item.
Readme item: Only one builder will work correctly if builders are scoped to include resource changes in other projects.
Couldn't you return in the "interesting projects" array the union of the interesting projects (build scopes) for all external builders on that project? That way you would be allowed to request deltas for all of those projects and you would then be called whenever any of those projects changed.
Yep...thanks John.
So forget everything I rambled on about the multiple builders not working. Fixed in ExternalToolBuilder.
Please verify DarinW.
Sorry, this is still not working correctly.
Fixed an NPE in this code.
Please verify Jared.
Verified.