Community
Participate
Working Groups
On some builds of AJDT, the timestamp of some plugins are different from the timestamp of the update site itself. This means that these builds cannot be installed because the timestamps need to be identical. I looked into the reason for this and it seems that the timestamp is not being properly passed into the pde build process, even though cruisecontrol sets it for the update site. Each feature therefore gets a new timestamp based on the current time that the build started (since it can't find the cruisecontrol timestamp). I have located this problem and will be submitting a patch soon.
Created attachment 116250 [details] patch to update the build process This patch updates the build process to include the new changes. Also included in this patch are other changes to the ajdt pde build to make it more consistent with the standard pde build.
Note that the main thing that had to change to get this to work was to ensure that the forceContextQualifier property was set before starting the build. Now it is set both in the build.properties and in the build-ajdt1.6.xml ant script on the build machine.
patch from comment 2 is in.
this problem has been fixed.
