Community
Participate
Working Groups
If a project contains two source folders, and one of the folders is also an output folder, a rebuild of the project can result in a number of errors that are not valid. Performing the rebuild again appears to correct the invalid errors. If the project only contains one source folder, that is also an output folder, the problem does not occur. The problem can be reproduced the first time a rebuild is done on a project that does not contain *.class files yet. The customer also occasionally sees the issue when doing builds (the customer stated that it appears to do a rebuild in some cases). Please note that along with having two source folders, with one of the folders also being an output folder, the problem is not reproducible using just any source code. The structure of the source code also appears to play a role regarding whether the problem occurs. The test case is not publicly available. Please contact support@oti.com for the test case.
moving to jcore
Please email the testcase.
Fixed & released into latest 2.1 build. This problem requires that the output folder is the same as one of the source folders, while another source folder has 'new' packages & types AND there are more than 1000 (our current limit) source files to compile. To work around this problem in 2.0.x builds, perform 2 full builds... the first full build will create all the packages in the 'output' folder & everything should work fine from then on.
Verified.
Ramp down policy was defined under http://wiki.eclipse.org/Stardust/Project_Plan/Ramp_Down
Sorry, ignore previous comment, was meant to be added to a different ticket...
