I am still -1. I don't see how this could possibly be less complex than
what we have now.
well - try to explain people how to build hibernateext! :)
I'm not saying it will be less complex for the core - it will be close to
equally
complex, but for hibernateext it gets easier!
(but again, its
Gavin King wrote:
I am still -1. I don't see how this could possibly be less complex than
what we have now.
We have things like "remember to build the Hibernate3 module before
building anything in the HibernateExt module" and we have hardcoded
paths to make it work. We have not only buildtime bu
Max Rydahl Andersen wrote:
On Tue, 04 Jan 2005 19:09:04 -0500, Gavin King <[EMAIL PROTECTED]>
wrote:
How will the user check out just the Hibernate3 core, from scratch,
without getting extra stuff??
Is that an important feature to have ?
Yes.
if that is needed we would add it as a cvs module t
On Tue, 04 Jan 2005 19:09:04 -0500, Gavin King <[EMAIL PROTECTED]> wrote:
How will the user check out just the Hibernate3 core, from scratch,
without getting extra stuff??
Is that an important feature to have ?
if that is needed we would add it as a cvs module to cvs, so a user would
e.g. do
c
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
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 toda
-1
This would make the HB3 checkout/build cycle much more complex.
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 hib
On Tue, 04 Jan 2005 15:38:10 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
Not really related but in HibernateExt you exclude the tests, the
build.xml, the docs etc etc
Is it still doable/better to keep a common-build.xml while not excluding
doc and test from the distribution of annotat
Not really related but in HibernateExt you exclude the tests, the
build.xml, the docs etc etc
Is it still doable/better to keep a common-build.xml while not excluding
doc and test from the distribution of annotations?
Max Rydahl Andersen wrote:
Hi guys,
HibernateExt and Hibernate core modules ha
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 ?
Alternative idea:
do it by copying instead of moving (less disruptive on people that has the
stuff already checked out)
just need to call it something
Max Rydahl Andersen wrote:
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-ap
11 matches
Mail list logo