Community
Participate
Working Groups
As recently discussed on cross-project list http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06289.html and in previous bugs, https://bugs.eclipse.org/bugs/show_bug.cgi?id=238606 sites that are "touched" in anyway that effects the directory time stamp are no longer considered mirrored ... even for a change which does not impact the artfacts themselves ... such as, say, changing the "name" of the repository in the artifacts.xml file ... at least for several hours, until all the "synchronizations" get caught up (which is usually relatively fast, if only "updating" one simple file. But still ... there could maybe be improvements.
I just use touch -t to change the timestamp on the repo directory to the time when the artifacts were first copied there and subsequently mirrored. This means when I update the compositeArtifacts and compositeContent jars to point to the child repo when the release is ready to go, but the mirrors still see the artifacts as being mirrored several days ago.
From what I see, the directory timestamp only gets changed if files are added or removed, so what I do is copy, say, the artifacts.jar file to another ~/temp directory, do the unzip and editing there, jar it back up, and then copy the artifacts.jar back to its original location. This seems to not change directory timestamps, so will still be considered "mirrored". (I'm not sure this is true for ALL flavors of Linux file systems ... but, seems to work with our current one). I have added this tip to http://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL#How_to_test.3F so will consider this bug fixed.
