JDO or Hibernate

We are in a planning phase for a project. In the past we have used JDBC, EJB and specific components for Data Access Layer.
We where evaluating different ways to be Database Independent as well as hidding the Object Relational Mapping.
The final contestent's are JDO's and Hibernate .

Can any one help us decide on what to go for and why?

Thanks guys.

This has been discussed quite a few times here and other sites. I would suggest you do a few searches in the forums to see some of the discussion. My view (trying to stay balanced) is try them both see what fits your needs (complexity) and requirements. Hibernate is a full featured ORM tool while JDO does not specialise in this area thus its lacking many features. This may not be a factor when you fit your requirements against the options as technical aspects may not be the only requirements in your list.

Thanks David,
I really did a lots of search and I got a lots of info. Some times too much info can also be confusing. I understand powerfull feaures vs portablity is currently the situation when you compare Hibernate vs JDO. It is really amazing to see the features of Hibernate. Most likely our choice will be Hibernate.

Also the portability argument for JDO in its current state is really a week one, because you will surely be forced to use vendor-specific extensions for a lot of more complex things.

Also keep in mind that the Mapping of relational tables is not standardised in JDO 1.x so portablility is mute anyway.