Thanks for the feedback.
On Wed, Jul 7, 2010 at 8:17 PM, Pete Muir <pmuir(a)redhat.com> wrote:
On 6 Jul 2010, at 13:31, Dan Allen wrote:
> Stuart also suggested renaming modules to trunk, or as I suggested making a
SVN-style symlink using svn:externals. The purpose would be to make it more obvious to
people what to checkout.
>
> /trunk -> /modules
No. This is completely counterintuitive and breaks all conventions around SVN.
Okay. I agree.
> I'd like to nuke the following directories from the Seam repo, which I don't
believe are currently being used.
>
>
http://anonsvn.jboss.org/repos/seam/trunk/ (each component has it's own trunk in
Seam 3, so this trunk is erroneous; all Seam 2 stuff is under a branch)
>
http://anonsvn.jboss.org/repos/seam/seam-gen/ (the real encore is in /sandbox)
Agreed.
Cool.
>
> I would like to consolidate /build and /dist under a single folder. They are both
build/packaging related and I think they should be seen as a single top-level unit. They
are this way in Weld.
No. These need to remain separate, they have different release cycles and thus different
trunk, branch, tag.
I'm assuming that's because the idea of a dist in Seam 3 is much different than
that of Weld. So the dist needs to be a separate entity. I'll include your points in
the readme.
It is - I actually screed this up in Weld a bit.
The idea behind a dist is that it represents the aggregation of released modules, whilst
build is something that each module depends on.
Looks like I never wrote this stuff up. It's back on the todo list.