This is perhaps not a maven question per se, but since I'm dealing with it in the context of untangling someone's existing maven project, I'll ask here...
We've inherited a large project which consists actually of 2 maven projects, each of which is a multimodule project. I'm trying to put some best practices in place, and in particular trying to fix things so that a developer can get up and running quickly, using the excellent jetty, hibernate, and hsqldb plugins. I'm trying to facilitate the hibernate3:hbm2ddl plugin and running into some wrinkles. 1) At the risk of sidetracking the responses to this email, is using hbm2ddl even a good idea? Coming (back) from the rails world, and also dabbling in the play framework, schema migrations seem a lot more comfortable than building schema directly off models. Always made me a little uncomfortable, not sure why. 2) The main question: The models for which schema need to be generated are spread among multiple modules in *both* projects. The approach I'm taking is to pick one of the maven parent projects and use that as the context for running hbm2ddl, but it's unable to find the entity classes that are defined in its submodules. I think I'm missing something pretty basic here. Am I better off moving hbm2ddl into a submodule, even though to some degree I would have to arbitrarily pick one? Or what do I need to do to get classes from submodules into the path for the parent pom? Thanks! dwh
