Home How to efficiently migrate old Hibernate tool (3.2.x) to newest Hibernate version?
Reply: 0

How to efficiently migrate old Hibernate tool (3.2.x) to newest Hibernate version?

Jssson
1#
Jssson Published in 2018-01-11 11:35:58Z

I am a master thesis student investigating the applicability of Autofetch-technology (see links) in real-world scenarios. There is a tool developed for this in Hibernate. However, the tool is legacy (developed for version 3.2) and the systems that I'm going to use in the thesis are using newer versions of Hibernate (4.x and 5.x). So before I can start evaluating the method in real-world scenarios, I need to somehow port the tool to the versions used in the projects that I will investigate in the study.

Since I don't have any background developing in Hibernate and software projects of this size, I need some advice. What type of workflow should I use to easily be able to test my progress for example? I tried just installing the tool onto the project using Hibernate (4.x) to see where the incompatibilities would occur, but I ended up in a situation where I couldn't distinguish whether the error is due to the configuration or incompatibility. I have also thought about making it into a Maven project, in order to handle the dependencies better. But I feel lost at this moment and I'm not sure how to proceed. For this reason, I ask you, what is an efficient way to go on about taking this legacy tool and migrate it to the latest Hibernate version?

For you who don't know about Autofetch: https://en.wikipedia.org/wiki/AutoFetch

The source code of the tool: https://sourceforge.net/projects/autofetch/?source=directory

The original auto-fetch article: http://www.cs.utexas.edu/~wcook/papers/AutoFetch/autofetch.pdf

Have a great day!

You need to login account before you can post.

About| Privacy statement| Terms of Service| Advertising| Contact us| Help| Sitemap|
Processed in 0.343431 second(s) , Gzip On .

© 2016 Powered by mzan.com design MATCHINFO