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,
>> 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
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
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
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 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
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
I am not happy with the way hibernate is built currently (see
http://in.relation.to/12116.lace for part of the details).
One thing I do not like currently is the way "release related" stuff and
"code" are mixed. To me, I'd really prefer that "release" be something
that was a separate "lifecycle"
