|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Nice, this sounds cool! I want to start building a JipiJapa integration module that does basic things like setting default properties for WildFly8, so the application doesn't have to but could override.
I'm currently not sure if we should create the ogm integration code in https://github.com/jipijapa/jipijapa or instead start a new repo at https://github.com/jipijapa/ogm that depends on https://github.com/jipijapa/jipijapa (for the spi mostly). I'm not yet sure of what the JipiJapa integration code needs to do yet but would like to start a project.
https://github.com/jipijapa/jipijapa kind of sucks (from a branch management point of view) in that I have a Hibernate ORM 3 subfolder, Hibernate 4.1.x subfolder and a Hibernate Hibernate 4.3.x subfolder. On the flip side, its easy to coordinate one set of branches for various needs and easy to release artifacts.
What do you think, does the OGM project deserve its own JipiJapa integration repo?