Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: hibernate
-
Labels:None
-
Number of attachments :
Issue Links
- is related to
-
NANO-132 hibernate3 module upgrade for hb3-FINAL VERSION! THERE IS API CHANGE!
-
Activity

Field | Original Value | New Value |
---|---|---|
Attachment | hibernate3.zip [ 14151 ] |

Attachment | hibernate3.patch [ 14152 ] |


Component/s | hibernate [ 10688 ] |

Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
This patch moves old classes to a new package, and it's impossible to see what changed. Wouldn't it make more sense to keep the original package name rather than having 2 sets of semi-identical nano-hibernate classes?