or, instead of java having a .sql script for that test data creation

On Wed, Apr 22, 2015 at 10:31 AM, Matthias Wessendorf <matzew@apache.org> wrote:
Looks like some odd things are going on here, w/ Sequences and Derby.... I have no clue - anyone else?

I tried other DBs (e.g. H2 or MySQL), but DBUnit is .... somewhat specific to Derby. Which is not great :-(

I move the migration merge to master to beta.1.  I am wondering if we really should do DBUnit w/ tests against Derby... especially since we only really support MySQL/Postgres.

I think what we should to is: get rid of DBUnit and use Java to create the test data. Use Docker (once fully supported on Travis) and fire up Postgres and MySQL during the tests.

-Matthias

On Wed, Apr 22, 2015 at 7:35 AM, Matthias Wessendorf <matzew@apache.org> wrote:
Hi,

as a FYI, the master branch now contains initial JMS support. That also means we require WF/EAP running as full profile, as stated in the updated README:


For the 1.1.0.Final release there will be a few more JMS based enhancements, as we go:

-Matthias



--



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf