Community
Participate
Working Groups
Our automated build attempts to build the command line compiler as org.eclipse.jdt.core_3.6.0.v_OTDT_r070_qualifier/ecj/global/ecotj-global.jar however, that jar file is essentially empty. Should investigate why this is so. Once we successfully build it, we should also copy it to the download area. (Currently all these steps are performed manually).
At a closer look our build first creates a good ecotj-global.jar but later replaces it with an almost empty file. The bogus second export is triggered from p2helper.xml: updateSiteExport -> doUpdateSiteExport -> <ant ... target="build.update.jar"> causing a bogus round of build.jars -> post.build.jars Hopefully this bug can be avoided by switching to PDE/Build's built-in support for creating a p2 repository. Documentation that should be helpful for this migration can be found in the online help of the PDE (searching the web only brings outdated info).
Indeed, "modernizing" our build scripts (r418 - r425) has fixed the double processing that deleted the successfully build jar file, which is found in testrun/build-root/src/plugins/org.eclipse.jdt.core_3.6.0.v_OTDT_r070_qualifier/ecj/global/ecotj-global.jar The remaining is just an issue of copying the resulting file to the download area, which will be done using a separate shell script (don't want this to happen for *every* build actually). I'm also still investigating whether "global" should be replaced by the actual buildLabel: should this be done during the build or afterwards when copying to the download area? I can switch between both behaviours using a one-line change in JDT/Core's customBuildCallbacks.xml (r446).
has been working in late builds.
