How will the user check out just the Hibernate3 core, from scratch,
without getting extra stuff??
Max Rydahl Andersen wrote:
On Tue, 04 Jan 2005 18:02:56 -0500, Gavin King <[EMAIL PROTECTED]>
wrote:
-1
This would make the HB3 checkout/build cycle much more complex.
eh - not really, the target is the direct opposite. It would from day
1 be exactly
the same for H3 as it is now. You just build it on its own as you do
today.
What will change though is that HibExt will have a much more
natural fit with the core (build wise)
As I said - checkout/build cycle will remain the same (you can
even just update the hibernate3/core subdirectory if you don't
care about getting update from the rest of the modules)
In eclipse you would also have a project per each (as you have today)
/max
Max Rydahl Andersen wrote:
Hi guys,
HibernateExt and Hibernate core modules have existed for some time now
as separate builds and it haven't been the easiest thing to maintain ,)
Before we had almost no dependency on the core in hibernateext, atleast
not on moving internal API's....now the story has changed with metadata
and the new tools (here also eclipse plugins).
I (and Christian) would like to merge the two modules so they follow
the
same structure and have well defined nice and simple structures.
The basic idea is simply to merge H3 and HExt into a similar structure
as HExt. Basically move H3 to HExt as a subproject (named hibernate
- or maybe just core ?)
so its under the same umbrella.
This will not change the release cycles or project naming it will
just make
the build and integration easier (compared to the current situation ,)
What do you say ?
Today we have:
/hibernate3/*
/hibernateext/*
/hibernateext/common/*
/hibernateext/metadata/*
/hibernateext/ejb-api/*
/hibernateext/tools/*
etc.
I suggest (with "renames" in ()'s)
/hibernate3/* (hibernateext/*)
/hibernate3/core/* (hibernate3/* + some stuff need restructuring
here but only minor - e.g. having src,test,grammar under a common
src/ root)
/hibernate3/common/*
/hibernate3/metadata/*
/hibernate3/ejb-api/*
/hibernate3/tools/*
I would like to perform this move via physical moves on the sf.net
cvs site to keep
the cvs history tracking in place. Any better suggestions ?
I think JBoss's new build structure follow this pattern too,
allowing for easier integration
into the QA stuff they are doing (but i'll have to check)
Any comments/suggestions/objections ?
--
Gavin King
+61 410 534 454
+1 404 822 8349
callto://gavinking
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://jboss.com
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
