You must have missed the discussion (on this list).  The tapestry4
layout is transitional. As we get things broken up a little and
converted into Maven2 builds, you'll see a more sensible layout.

On 4/22/06, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
> I think the current repo layout is somewhat confusing, by my point of view.
>
> I see tapestry5 main dir as the trunk/HEAD/CURRENT which involve the
> development of the leading edge features and improvements while
> tapestry4/trunk and all dirs under tapestry4/branches/ (which includes
> old released/tagged/branched code) under the main branches directory,
> i mean, they are indeed branches, don't they?
>
> I would lay it out as follows:
>
> At the root only the canonicals:
> branches/
> tags/
> trunk/
>
> under trunk the current content of tapestry5/trunk (as a maven2
> multi-module project).
> under branches the content of tapestry4/trunk in a branch called
> (let's say) 4 and all the branches under tapestry4/branches.
> tags remains untouched.
>
> While if you wish to have different development life cycle for the
> different modules under tapesty5/trunk (just as tapestry-core) i would
> pull up tapestry-core (and all the future modules) to the root and
> give it a trunk directory.
> But i would rather go for a trunk which contains a "maven2
> multi-module" project.
>
> Which is the purpose of the current layout?
>
> As i said these are my .02 euro-cents so thanks for take time to read it
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to