- This topic has 20 replies, 4 voices, and was last updated 17 years, 2 months ago by Riyad Kalla.
-
AuthorPosts
-
Steve PriorMemberDid you guys run into a major issue that stopped the release this weekend, or can we expect good news any minute now?
Riyad KallaMemberWe ran into some annoying little stuff that would just piss folks off if they ran into it, management decided to hold back and stomp on them. Last minute documentation polish, also found some last minute breaks in wizards with some corner case stuff that we know we couldn’t ship (like 2 faces-config.xml files caused the JSF wizards all to get confused and die)
We are literally down to the last 10 incidentals to knock out. It has to go out the door by Wed at the latest though.
On a side note, this release was suppose to be fairly simple because of the entire product transition ontop of 3.3, but it ended up being pretty major. Just checked our tracker and it ended up being over 300 changes/features/fixes.
Steve PriorMemberThanks for the info. As for some of those nits, keep in mind that the software industry in general pretty much expects a bug fix release for all major releases, so we won’t actually fully trust it until there’s a 6.0.1 release anyway 🙂
Any chance my favorite nit – that Hibernate 3.2 should be an option for “Add Hibernate Capabilities” and not just available through “Add JPA capabilities” will make it into 6.0?
Riyad KallaMemberDoh, no luck there. We added JPA-Spring integration instead. Unfortunately official Hib 3.2 support isn’t just libs, it’s also annotation support, working on the rev-eng code/wizards and all that jazz, so we had to make a choice.
Sorry about that.
Steve PriorMemberWhile official Hib 3.2 support might include that other stuff, there is nothing crazy about using exactly what “Add Hibernate Capabilities” does now, but choosing to use the Hib 3.2 libraries instead of 3.0 or 3.1. The workaround is to select 3.0 or 3.1 when running “Add Hibernate Capabilities”, but then changing the classpath to include the 3.2 libraries instead, it’s a nit that you can’t go there directly. The code currently generated works just fine with 3.2. This allows a developer to use the same code, but against athe latest version of the libs with the most currrent bugfixes. For example I know that 3.2 has a change which allows it to handle inserts to a table using an index from a sequence in one operation instead of a seperate select nextval from the sequence follower by an insert. This can be a major performance boost to an existing application, but doesn’t require the other stuff you mentioned.
Riyad KallaMember6.0 GA should hit the update site here in the next few hours, then the announcement, then the download section should get updated later today.
-
AuthorPosts