[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12597: --------------------------------------------- Tomas, don't recall us ever promoting this project more than "on a best effort basis". If you want Hibernate 4 support (which makes perfect sense) then the best way to make it happen is to contribute a patch. Once we get our modules migrated to Git that should be even easier btw. -- 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

[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ] Tomas Vala commented on JBIDE-12597: ------------------------------------ Hi Max, thanks for respose. For record, over the time I have managed to make the Plugin work with: - Hibernate 3.6 - Hibernate 4.x Add support for Boolean data type (which was sadly overlooked in original implementation and is essential for real-life use). Changes listed above required (rather minor) modifications of source code. I could commit these changes back, but there are some issues to point out: 1. Plugin uses Hibernate APIs that received backward incompatible changes between 3.5, 3.6 and 4.x. Therefore Plugin stopped working with each of named Hibernate releases. 2. Due to nature of incompatible changes I can't make the plugin work with all 3.5, 3.6, 4.x releases at once. Not the easy way at least. Maintaining three program paths / branches is not convenient either. 3. Not being an expert on Hibernate internals I really can't give proper statement on whether Plugin uses the best suiting, stable public APIs, or it adheres to rather hacky ways, making it sensitive to changes made in Hibernate. Perhaps Hibernate offers more abstract APIs that would make the Plugin resistant again future internal Hibernate changes. I really don't know at this point. Assuming I would go on with commiting my modifications would it be for you, as a project initiator and maintainer, acceptable to drop support for all Hibernate versions older than 4.0? That said the current state of Plugin in official repository doesn't support rich variety of Hibernate releases either as is only works with nowadays outdated 3.5 (and perhaps older ones). :-) Tomas -- 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

[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12597: --------------------------------------------- just to be clear on what i'm saying - I do not think this birt/hibernate integration should be part of eclipse tooling - it should be a framework/integration on its own. -- 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

[ https://issues.jboss.org/browse/JBIDE-12597?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12597: --------------------------------------------- if you follow jbosstools-dev list you can see we are currently trying to migrate from svn to git and that explains the current temp-jbosstools-* repos on github. Thus don't rely on these yet - its just temporary repositories used for testing the migration. You can though go and fork this repo now and once we get the real repo up and running you can submit pullrequests for the changes (maybe outline on jbosstools-dev, the forum or in related jira what changes you wanna suggest..?) -- 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