Community
Participate
Working Groups
It looks like the ecf p2 repos were recently reorganized. They used to look like this http://download.eclipse.org/rt/ecf/integration/platform/v2010-09-06_07-22-05 now they look like this kmoir@dev1:/home/data/httpd/download.eclipse.org/rt/ecf> pwd /home/data/httpd/download.eclipse.org/rt/ecf kmoir@dev1:/home/data/httpd/download.eclipse.org/rt/ecf> ls 3.2 3.3 3.4Test It seems that the old bundles that we consume in our builds are missing. For example kmoir@dev1:/home/data/httpd/download.eclipse.org/rt/ecf> find . -name org.eclipse.ecf.provider.filetransfer.httpclient.ssl.source_1.0.0.v20100906-1425.jar kmoir@dev1:/home/data/httpd/download.eclipse.org/rt/ecf> Could you please restore your old repos, or point me to the new location? It would have been nice if this change had been mentioned on the cross-project list.
Markus could you please look at this...I think it probably has to do with the EF-requested clean up/archiving.
(In reply to comment #0) > Could you please restore your old repos, or point me to the new location? It > would have been nice if this change had been mentioned on the cross-project > list. The bits have been moved to archive.eclipse.org as part of ECF 3.4 release preparations (bug #321674). As we have pointed out numerous times before (bug #314901 comment 7/17 bug #321676 bug #219499), ECF does not have the releng resources to provide the platform with a special/dedicated build. Platform will have to consume our regular releases.
Okay, could you please the p2 team on the bugs when you archive your repositories so our builds don't break? Or send a note to p2-dev? It's good to know when you archive your repos so we can update our map files to point to the new location.
(In reply to comment #3) > Okay, could you please the p2 team on the bugs when you archive your > repositories so our builds don't break? Or send a note to p2-dev? It's good to > know when you archive your repos so we can update our map files to point to the > new location. What's the p2 team's bugzilla address to use for releng bugs? We will try our best to keep p2 informed, but in general we don't have the resources to notify each ECF consumer individually about releng changes. It might be safer to subscribe to the ecf.releng inbox. Btw. since we are not going to remove anything completely, what about changing the platform build so that it tries archive.e.o if download.e.o fails.
What's the p2 team's bugzilla address to use for releng bugs? >>equinox.p2-inbox@eclipse.org thanks :-)
