Hi
All,
I am in charge of
creating a preconfigured internal release of eclipse 3.2 for my company. Once
developers have installed the baseline product I would like to use the update
manager to handle *all* enhancements (via feature installs) and updates (to the
core platform and Callisto features).
I have read the
docs on controlling the eclipse update policy (http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-37.htm).
Do you think it is necessary to create internal proxies for the core sites
installed by default in 3.2 ('Callisto Discovery Site' and 'The
Eclipse Project update site')? Does anyone have any experience of doing this? I
would be especially interested in hearing about the process by which you detect,
install, test and then expose updates to your company via the proxies. (We have
a number of home grown and vendor features that would need regession testing
with all updates before enterprise wide relase.)
Best rgds,
Miles
----------------------------------------------
Miles Daffin
Morgan Stanley | EAI | MSDE
20 Cabot Square | Canary Wharf | London E14 4QA |
UK
Tel: +44 (0) 20 767 75119