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

The only issue there is that then people get all the tags and branches of the modules. I'm inclined to just start with the README.txt that references the checkout command we created and see how far that gets us. -Dan On Tue, Jul 6, 2010 at 4:18 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: As I mentioned in the last IRC meeting, there is some cleanup that needs to be done on trunk. The directories currently getting attention are fine. It's the cruft that sits around them that needs to go. It's making it really difficult for newcomers to understand what the heck to checkout. I'll also put together a brief README.txt that simply explains the purpose of each root-level directory. 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)

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.

http://anonsvn.jboss.org/repos/weld/build/trunk/ I'll do the cleanup tomorrow unless I get feedback otherwise. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Thanks for the feedback. On Wed, Jul 7, 2010 at 8:17 PM, Pete Muir <pmuir(a)redhat.com&gt; 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.

On 7 Jul 2010, at 18:52, Dan Allen wrote: > Thanks for the feedback. > > On Wed, Jul 7, 2010 at 8:17 PM, Pete Muir <pmuir(a)redhat.com&gt; 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. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev