Hi Mladen,
Costins README.txt inside the sandbox already suggested:
===
Sandbox components should be developed in a sub-directory of the /tomcat/sandbox
directory. Developers may choose whether to add source directly under the
component's directory or to create the standard subversion /trunk/, /branches/
and /tags/ directories and add the source under the /trunk/ directory.
The svn commands to do this will look something like:
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/trunk
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/branches
svn mkdir https://svn.apache.org/repos/asf/tomcat/sandbox/component/tags
Alternatively, you can use the java/ directory. If possible:
1. create a new package ( or few ) for each module
2. if you have an external dependency for an optional component - create a new
package.
3. Update the top level build.xml file with targets for your module - use
<include> patterns instead
of exclude.
The single tree may help increase visibility of the source code. We are in 2005
( or more ), build tools
and IDEs have very good support for include/exclude patterns, we have tools to
find dependencies between
packages, and we have a single community, so we don't need fragmented source trees and more, at least in
sandbox.
===
+1 for the "components" way of doing it. More precisely to prevent
duplicate trees, component should include a more precise description of
the issue, otherwise we might soon end up blocking general dirs like
"cluster", "connectors" etc.
Regards,
Rainer
Mladen Turk schrieb:
Hi all,
IMO this is mostly Costin related, because he has something
inside the sandbox :)
Now my question is, could the current sandbox content be
moved to the /sandbox/abc so I (or someone else)
can create a /sandbox/xyz ?
Right now the sandbox is not the 'sandbox' but rather
the Tomcat6Sanbox thought.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
