Community
Participate
Working Groups
Build Identifier: M20100909-0800 After fixing the bugzilla 318331, the HoldsOptions.needsRebuild() method asks if the parent needs a rebuild. However, after the build is done and HoldsOptions.setRebuildState(false) is called, the parent build state is not cleared in this method, assuming the parent will be called explicitly with setRebuildState(). This, however, does not always happen. I observe a situation where a tool has a parent, which is a schema root of this tool, i.e. without random id. Both tools have inputType objects with two different random IDs. The setRebuildState(false) is never called for the inputType belonging to the parent. So, perhaps setRebuildState() should also call the parent in the same manner as does needsRebuild()? This doesn't reproduce in the GNU toolchain, but shows in a custom toolchain. It appears depending on a toolchain definition, because one other custom toolchain doesn't show this problem. Reproducible: Always
Created attachment 196564 [details] A patch clearing rebuild state of the parent toolchain object
As a result, the project rebuilds every time. The bug appears only for some toolchain definitions. It depends on how the toolchain is defined in plugin.xml.
I have this issue as well in a custom toolchain and added my vote to have it fixed.