com> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MMS-Smtp-Program: Macallan-Mail-Solution; Version 4.6.0.1 X-MMS-Smtp-Auth: Authenticated As [EMAIL PROTECTED] X-MMS-Smtp-Mailer-Program: Macallan-Mail-Solution; Version 4.6.0.1
I don't have a good pulse on the "majority of users" but I would suggest we switch to Tomcat as the default (Jetty has probably had most of its bugs worked out by now) and update the Welcome page with instructions on how to switch (or point them to the Release notes) and we focus on resolving this issue in the installer for 1.0? - Matt Dain Sundstrom wrote: > > On Oct 11, 2005, at 7:41 PM, Dave Colasurdo wrote: > >> 2) Have a separate binary image for both the Jetty and Tomcat >> webcontainers. I'm not suggesting biting off the whole task of >> revising the assembly process but rather just merely having two >> binaries each with a separate set of config files (config.xml, >> config.list). This could even be a post-build step done on the >> common image. This isn't very technically interesting but clearly >> communicates to users that there are two separate environments and >> they select the download that they want. Of course, this goes away >> if/when the assembly revision is complete. > > > +1 this is a reasonable compromise. > > -dain > > >
