Java 1.4 has been end-of-lifed: The EOL transition period began Dec, 11 2006
and will complete
October 30th, 2008
http://java.sun.com/j2se/1.4.2/
Let's not IE6 this -- kill it, kill it now, kill it dead, and no more support.
~~ Robert.
Christian Maslen wrote:
Voxland, Nathan wrote:
Is
If only it was that easy! 1.4 is the backbone of huge numbers of application
servers still in active use out there, because JavaEE only recently got
updated. These are also the environments where a tool like liquibase comes in
most useful. I'd love to see the death of Java 1.4 as much as
I don't care much about this, but I think that anyone who still needs Java 1.4
can download a previous version of Liquibase and use it, right?
Diego
- Mensagem original
De: Paul Keeble cs...@yahoo.co.uk
Para: liquibase-user@lists.sourceforge.net
Enviadas: Segunda-feira, 20 de
Developer A should have merged from the SCM, then done a complete
re-test, including rebuilding the database. At least, that's how I see it.
Yep, that is another solution I'd forgotten, but it is also one I was trying to
avoid. In general, I would not recommend rebuilding the database
I would agree that testing the migration should be a part of the
development process, but I think of it as a level of testing that comes
after my software. First and foremost, the software has to work with
the version of the database that it is designed to run against. I do
understand that
