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> 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