I'm still not sure if I completely understand the approach for "easy
switching from Jetty->Tomcat".
- If applications have already been deployed to say Jetty before the
switch is made, then are they functional in Tomcat?
- If not, can the same application be deployed in Tomcat such that it
doesn't affect the Jetty application if the switch is reversed at some
time in the future?
- Finally, how are applications that must be "pre-deployed" in each
container managed (for example example the web console)?
Joe
David Blevins wrote:
LAST ISSUES
- Easy switching from Jetty -> Tomcat
- Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
ServiceMix=>Hiram, tmpOrb=>Dain)
- Version number of some sort in the schemas?
Is there anything else people think *must* be there to ship?
THE FINAL STUFF
Again, we have to run the TCK on the final binary. It would be great
if we could cut the final release by Wednesday and be finished TCK
testing by Friday. To get there we will have the standard checklist of
stuff to do:
1. clean the jira
2. create release notes
3. update readme files
4. Change the version number in etc/project.properties and the plugins
5. Create our tag
6. Cut and sign the binary and source distributions
Then it's just test and vote, both take two days and can be done at the
same time.
Any details I've missed?
-David
--
Joe Bohn
[EMAIL PROTECTED]
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
