You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by co...@apache.org on 2005/10/28 05:01:22 UTC
svn commit: r329055 - /tomcat/sandbox/README.txt
Author: costin
Date: Thu Oct 27 20:01:20 2005
New Revision: 329055
URL: http://svn.apache.org/viewcvs?rev=329055&view=rev
Log:
A small comment on source organization.
Modified:
tomcat/sandbox/README.txt
Modified: tomcat/sandbox/README.txt
URL: http://svn.apache.org/viewcvs/tomcat/sandbox/README.txt?rev=329055&r1=329054&r2=329055&view=diff
==============================================================================
--- tomcat/sandbox/README.txt (original)
+++ tomcat/sandbox/README.txt Thu Oct 27 20:01:20 2005
@@ -33,6 +33,16 @@
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.
Releases
========
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org