Correct, the new model (annotation based) is modeled after a fashion by
TestNG. You have a set of classes which contain migrations.
The current version uses classes extending from a Migration interface. I'm
also only targetting PostgreSQL so far ( at least on the database creation
side, but having to look at how to automate this for Sybase shortly ).
On 3/27/07, Tyler Nelson <[EMAIL PROTECTED]> wrote:
Hi Mark D,
This sound very interesting and what was kind of what I was
envisioning,.
The caveat for us is the we are still on Websphere 6 so no annotations :(.
I'm guessing that the annotations would need to be added to application
classes, is that correct?
Still let me know when you put this up on GoogleCode, I am still
interested
in seeing it.
Thanks,
Tyler
On 3/26/07, Tyler Nelson <[EMAIL PROTECTED]> wrote:
>
> Hi Mark,
> I will check them out.
>
> Thanks for the links,
> Tyler
>
>
> On 3/26/07, Mark Hobson <[EMAIL PROTECTED] > wrote:
> >
> > On 26/03/07, Tyler Nelson <[EMAIL PROTECTED] > wrote:
> > > Does there happen to be a plugin to handle database migrations for
> > Maven 2.
> > > I was thinking something like what Ruby on Rails does.
> > >
> > > If not what are some of the best practices for doing DDL and DML
with
> > maven,
> > > which part of the maven lifecycle have others put this type of
> > behavior?
> >
> > DdlUtils [1] is handy for DDL and DML work. Also check DDLUTILS-59
> > [2] for an initial Maven 2 plugin.
> >
> > Mark
> >
> > [1] http://db.apache.org/ddlutils/
> > [2] http://issues.apache.org/jira/browse/DDLUTILS-59
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
