Tobias, Christophe, there's a question for you at the bottom, but everyone else should still read on.
The MySQL DDL script was autogenerated (with some script mangling) by Felix and the JPA bindings. Unfortunately, the bindings aren't terribly intelligent and only generate the DDL script for each bundle *when the database is first accessed from that bundle*. This means that lots of the tables are created by the integration tests, but some must be caught manually (at least for now) like upload, and annotation. A bundle which does not have an integration test which triggers its database functions, and has no rest endpoints to manually trigger things presents a problem: I can't generate the DDL! This isn't to call out anyone, just a note that I would like people to keep in mind when developing. It's easy to forget things like this when they're not something you have to work with, but they can block (or break!) releases if they're not caught. Hopefully for 1.4 we won't need to generate the DDL, but we haven't gotten that working quite yet :) Tobias/Ced: The OAIPMH appears to be one of the bundles which has this issue. How would I go about firing the database functionality? G
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
