On 12-05-04 07:02 PM, Mick Semb Wever wrote:
My understanding is that it was the idea to spin out request and autotag
as separate projects upon release. The poms in request, autotag and
tiles-parent were designed not to rely on a project in the first place
(they're based on tiles-master directly).
That's correct, as long as we don't collide with apache's distaste of
umbrella projects. ref
http://thread.gmane.org/gmane.comp.apache.tiles.devel/180/focus=182
It's funny in that thread that we never touched on the subversion
layout, i'm glad one way or another that you brought it to attention.
Thanks for the pointer. I admit I didn't read the dev archives that far
into the past.
I'm not sure I understand the details of the "umbrella" issue, why
apache dislikes it.
I agree with Antonio about the release being a nightmare with the
separate version management, and the "one command build" was very useful
until the release indeed.
But actually it's only the first release that is painful. Once version
1.0.0 is out, it should be much easier to move on. Actually it may even
be easier, since we won't have to release tiles-request if we just want
to add a new option to the tiles.xml syntax.
And the "one command build" will be much less needed once the basic
dependencies (like tiles-request-api) are available in maven central.
Soon! In the mean time, the old structure is still available under the
tag tiles-3-reactor.
Nick.
