In the words of Arnaud (commenter on the blog), isn't the GateIn
approach what you want ?
1 project with submodules, all have the same version thus the parent is
the reactor ?
btw. I remember we initially did this parent were put in a dir on its
own to make eclipse
happy - that is not really a
On 09/11/2009 02:07 PM, Max Rydahl Andersen wrote:
> In the words of Arnaud (commenter on the blog), isn't the GateIn
> approach what you want ?
>
> 1 project with submodules, all have the same version thus the parent is
> the reactor ?
>
> btw. I remember we initially did this parent were put in
Hi,
I am just wondering if you could elaborate what exactly the problem with
the release.
I think so far you are the only one who actually did a release for Core
using the current setup.
Hibernate Search and Validator also use the maven release plugin and there
is works just fine.
Admittedl
On Fri, 2009-09-11 at 14:07 +0200, Max Rydahl Andersen wrote:
> In the words of Arnaud (commenter on the blog), isn't the GateIn
> approach what you want ?
>
> 1 project with submodules, all have the same version thus the parent is
> the reactor ?
Different discussions. The "GateIn approach" is
Hello everyone.
We are currently using Hibernate Shards 3.0.0.b2 (which is from 2007...) and
I need to get the HSHARDS-52 (
http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-52) patch
applied.
Tried to figure out the documentation on building the trunk source with ant
but it seems t
Hi Aleksander,
I've never built Shards myself, but from your problem descriptions I take
it that the Shards setup
is the same as for Annotation, EntityManager, ... pre maven migration.
If so you need a hibernate 3.2 core checkout as well. In the core module
you run:
'ant clean jar prepare-dir
In the words of Arnaud (commenter on the blog), isn't the GateIn
approach what you want ?
1 project with submodules, all have the same version thus the parent is
the reactor ?
Different discussions. The "GateIn approach" is *functionally* no
different than what we have today Max. The o
>> 1 project with submodules, all have the same version thus the parent is
>> the reactor ?
>>
>> btw. I remember we initially did this parent were put in a dir on its
>> own to make eclipse
>> happy - that is not really a concern anymore since later eclipse
>> versions can handle
>> having a root
Its not the release per-se alone. These are not all directly related so
its hard to explain...
I outlined in the other email to max about checking out and needing to
immediately install everything. Granted, it depends on exactly what you
want to do, but that's the basic requirement; for example,
