One of the problems with the Hibernate Tools plugin today is that in order to generate from a database, you must type the configuration options every single time you run the plugin. I think it would be great if we could tie this plugin into the Forge configuration system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level specifically when requested - see: getScopedConfiguration(), but by default it will access the project level configuration first, then fall back to the user configuration if that cannot be found or does not have an entry. In this case, using the default behavior should be the right behavior.
One of the problems with the Hibernate Tools plugin today is that in order to generate from a database, you must type the configuration options every single time you run the plugin. I think it would be great if we could tie this plugin into the Forge configuration system/API.
// org.jboss.forge.env.Configuration;
@Inject Configuration config;
The configuration API can save and load data at the project/user level specifically when requested - see: getScopedConfiguration(), but by default it will access the project level configuration first, then fall back to the user configuration if that cannot be found or does not have an entry. In this case, using the default behavior should be the right behavior.