[Bug 826701] Review Request: hibernate-tools - Hibernate tools

bugzilla at redhat.com bugzilla at redhat.com
Mon Aug 13 12:45:01 UTC 2012


https://bugzilla.redhat.com/show_bug.cgi?id=826701

--- Comment #7 from Marek Goldmann <mgoldman at redhat.com> ---
Some information about versioning of Hibernate Tools.

Old SVN repository should not be used.

On GitHub there are 3 branches:

- 3.4.x - supoprt for hibernate-core 3.3-3.5
- 3.6.x - support for hibernate-core 3.6
- master - support for hibernate-core 4

These 3 versions have different API's and most probably we'll need to package
two or all of them.

There are no tags at this moment, it should be fixed in the future.

Some more info about why we need to have available multiple versions of these
libraries. Since we have hibernate3 package and hibernate (4) in plans I
thought about having two packages available in Fedora:

1. 3.6.x (hibernate-tools36 package) branch and
2. master (hibernate-tools package) branch

But it seems that the 3.4.x branch also needs to be packaged, because the some
main code in Hibernate Tools requires it and we would end up in some
incompatibility issues:

12:32 <@maxandersen> mgoldmann: when you create a project in eclipse it has
some 
                     metadata in the .settings folder.
12:33 <@maxandersen> mgoldmann: if you share this with another team member (you 
                     often do to avoid reconfigure projects) they will not 
                     load/behave differently.
12:33 <@maxandersen> mgoldmann: and if you don't do that - there is the
mechanism 
                     that uses mvn to let its pom.xml configure your project
based 
                     on pom.xml and this would also be a bit funky if 3.5 is 
                     "nothere"

(there is a typo above and 3.5 should be read 3.4)

If this package is not immediately needed, I would postpone it and get back to
it once it'll be a hard stop for someone. In the meantime we can find a
solution to satisfy all requirements. If any.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



More information about the package-review mailing list