| [swtbot-dev] SWTBot update-site |
|
Hey Ketan, I've been trying a new approach to define our target platform and I've run into some irregularity in SWTBot's update--site. What I'm doing now is I am mirroring the update-site on my local file system using p2 (for both 3.4 and 3.5): ./eclipse -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication \ -source http://download.eclipse.org/technology/swtbot/ganymede/dev-build/update-site/ \ -destination $DESTINATION However, when I run this I get some weird stuff in the $DESTINATION/plugins folder. In both case (3.4 and 3.5 update-site), I get: org.eclipse.swtbot.ant.optional.junit3_2.0.0.506-dev-e35.jar org.eclipse.swtbot.ant.optional.junit3_2.0.0.512-dev-e34.jar org.eclipse.swtbot.ant.optional.junit3_2.0.0.512-dev-e35.jar org.eclipse.swtbot.eclipse.junit3.headless_2.0.0.506-dev-e35.jar org.eclipse.swtbot.eclipse.junit3.headless_2.0.0.512-dev-e34.jar org.eclipse.swtbot.eclipse.junit3.headless_2.0.0.512-dev-e35.jar which is very weird. The 506 version should not be there, the junit3-3.5 bundles should not be in the 3.4 update-site and vice-versa. I can work around this right now by manually removing the wrong versions, but I'd like this process to be automatic so it'd be nice if the update sites were clean. p.s.: I know I should probably be building the target platform using p2 director, but I can't right now (for various undefined reasons...) so I'm using the mirroring as a workaround. p.s.2: I just tried mirroring the helios update-site: same thing, there is e34 and e35 versions of the junit3 bundles. Thank you for your time. --
Pascal Gélinas | Software Developer Nu Echo Inc. 1435, Saint-Alexandre, Suite 200, Montreal (Qc),Canada, H3A 2G4 Tel: (514) 861-3246 ext 4234 | FAX: (514) 861-1676 Pascal.Gelinas@xxxxxxxxxx | www.nuecho.com | blog.nuecho.com Because performance matters. |