Group items tagged

t just works - Migrate from any version (incl. an empty database) to the latest version of the schema Automatic migration on startup - Ship migrations together with the application and run them automatically on startup Convention Over Configuration - Classpath Scanning to automatically discover Sql and Java migrations Plain Old Sql - SQL scripts for regular migrations (incl. placeholder replacement). No proprietary XML formats, no lock-in. No limits - Java classes for advanced migrations Highly reliable - Safe for cluster environments (Multiple machines can migrate in parallel) Maven support - Maven plugin for migrating manually Fail fast - Inconsistent database or failed migration prevents app from starting. Schema Clean - Drop all tables, views, triggers, ... from a schema without dropping the schema itself

This blog host some of the good article on Java, FIX Protocol and Tibco Rendezvous messaging. I have shared Interview questions, daily tips, commands and approach on how to increase productivity and work effectively with these technology.

" Should you need to compile an OT/J program outside the OTDT, the following steps should enable you to use ANT for this task: download ecotj.jar you'll always find the latest version here in the column "Command Line Compiler" add it to your ANT runtime classpath (either place it in your ant_lib directory or provide the path by a -lib command line option to ant). in your build.xml set the property build.compiler to use the OTDT compiler in tasks, like that: "

"The past year I've been learning a lot of Scala and I'm currently working on a new project using Scala. I use LiquiBase, which is a database-independent library for tracking, managing and applying database changes. I'm also using the simple-build-tool (SBT) for my project. So I've put together a little SBT plug-in for running LiquiBase maintenance commands (update, rollback, …) from within SBT. For example, whenever I want to apply new database changes with LiquiBase I can now simply run sbt liquibase-update which sets up a new instance of LiquiBase and executes the LiquiBase update command which migrates my database to the latest version. At the moment the plug-in supports the following commands: liquibase-update, liquibase-drop, liquibase-tag, liquibase-rollback and liquibase-validate. What are the benefits of using the plug-in and not just the LiquiBase CLI? * no download/install of LiquiBase * classpath handled by SBT * no need to provide a big list of parameters or writing shell scripts The plug-in is called liquibase-sbt-plugin and you can find it here on GitHub. Feel free to use it or fork it and suggest changes. I'm still relatively new to Scala and especially SBT so any remarks are very welcome."

In this article I'll describe the setup I use to do develop Lift applications. While more heavy-weight than if an interpreted language is used, I find this setup provides fairly decent turnaround times. So, it took a little longer than expected to write this article which continues where the previous stopped. But all good things come to he who waits The software used in the previous article all had major updates in the meantime: Scala 2.8 (2.8.1 is just around the corner) Eclipse 3.6 Scale IDE for Eclipse (though a nightly build is currently needed for Eclipse 3.6) Gradle 0.9 RC1 Lift 2.1 RC2