vyemialyanchyk wrote:
may be you give up too easily?
I can't say my experience has been pleasurable. I had expected to introduce Hibernate, spend a week or two dealing with the inevitable tweaking and configuring, and be done with it.
I'm currently tallying several person-weeks and counting.
The worst thing here is the docs. I'm on reverse engineering, Java SE and using annotations (which were announced as the Next Great Thing), just to find out that all the docs are written with forward engineering, Java EE and .xml files in mind. To add insult to injury, there's some fine print neither annotations nor reverse engineering can do everything that .xml can.
I'm not sure that I'd use Hibernate if I had known beforehand. I know it has a lot of things under the hood that I couldn't duplicate easily, but the initial barriers are extremely high and extremely expensive to scale.
To set up a new project for Hibernate today, I'd recommend either having a Hibernate guru on the team, or hiring one for a week (at least).
vyemialyanchyk wrote:
just a question why this is necessary for you?
if you wants to contributes, you should spend a time to study how it works internally...
as I remember, it takes a couple of days to install environment,
the main problem here - put sources in proper place, for this just necessary to observe
configuration of the paths... only you could configure this on your machine...
Paths can be made relative to the project. (Keep the jars etc. in a directory inside the project tree.)
max wrote:
File > New Java Project > Use existing directory and eclipse includes it.
Ah.
I was trying Import... > Project, which didn't work.
Then I tried File > New Project > Plug-in Project, which wouldn't work either.
Unfortunately, the project is not self-contained. It is missing ant.jar, and I have no idea which version to install (and I'm not going to install some arbitrary ant.jar and end up in jar hell).
Also, I spent some time fiddling with the compiler settings to get the warning count from 2600+ to a more sane 158.
There should really be a .settings/org.eclipse.jdt.core.prefs file in the repository.
What's also missing is a .project file (for File > Import...).
A renamed copy of .classpath would help, too. At least I'd notice what .jars I'm missing, even if they happen to reside on another path than what I have.