Has anyone successfully used hibernatetool with gradle?

I sort of got it to work using what seemed like a convoluted path, and
I'm wondering if there is an easier way.

In the past I have had a db domain project, and its build.xml had
targets like "drop" that would use the hibernatetool ant task to drop
the database.

With gradle, I couldn't figure out how to tell hibernatetool to put
build/classes on its classpath.  Things quickly got a bit ugly ... where
to put hibernate.cfg.xml, for example, so that we don't violate DRY, and
still have it configurable with username & passwords, etc.  It works,
but it's not exactly better than the old way, which makes me think I
must be thinking about it wrong, or missing a fundamental concept (it's
my first day with gradle...).

My work around was to create a peer project that uses my db domain
project, but I'd really much rather not do that since it's a pretty big
structural change for a relatively minor little feature.

Any suggestions?

Thanks,
Eric
-- 
View this message in context: 
http://www.nabble.com/hibernatetool-tp21142283p21142283.html
Sent from the gradle-user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to