Thanks for the info Sachin. -----Original Message----- From: Sachin Patel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 28, 2006 8:47 AM To: [email protected] Subject: Re: Release Management
FYI The eclipse update manager can be run headlessly and it can be used not just to install "features/plugins" but it can be used to install any type of archive and to any target with the use of custom InstallHandlers so technically it could be used to update G. I don't know offhand how much a standalone update manager pulls in and how much overhead there would be, but I think its something definitely to look into. - sachin On Mar 27, 2006, at 10:21 PM, Matt Hogstrom wrote: > Jeff, > > We are constantly kicking around ideas of how to improve the user > experience. It sounds like your primary concern is updates and > syncronization when running in Eclipse or another IDE. Is this > correct? Do you have requirements for runtime updates as well? > > Bradford, Jeff L wrote: >> One of the issues we have run into with previous open source app >> servers >> is the lack of a fast migration path from one version to the >> next. It >> is always an unzip and then a manual movement of the needed app >> specific >> info and server config while keeping in mind changes to DTDs as well. >> Keeping a large development shop on the same version of an app server >> locally and on our various testing tiers is a major undertaking. >> Therefore, do you have any plans or would you consider assembling >> some >> type of auto-update executable, script or an Eclipse type of Software >> Updates option to ease this pain between major and minor versions. >> Thanks, >> Jeff
