As the community forms, we need to formalize these guidelines, especially to differentiate
'requirements' from suggested 'guidelines'.
Shane's starting proposals:
@@ -54,28 +105,32 @@ xml-commons/
README.html - this file
build.xml - overall build file for top-level items
xdocs/ - top-level xml format docs about this project itself and our guidelines
- (in stylebook format like xml-xalan uses, unless someone wants to volunteer to start
- out with another format and maintain it)
+ (in whatever format xml.apache.org uses for site)
docs/ - (not checked in) html format docs created by 'build docs' from xdocs
java/ - root of all java-related files
- build.xml - Ant build file for all java files (might call subsidiary build files)
external/ - src root of all source files in java that come from external sources
for example: the DOM, SAX, and JAXP files
org/xml/sax/*
org/w3c/dom/*
javax/xml/*
-
- apache/ - src root of all source files in java that are apache-owned
- tbd/ - java packages added as needed
+ external/build.xml - Ant build file for all external sources
xdocs/ - xml format docs describing any java files, as needed
+
+ {name}.xml - Ant build file for Apache-defined subproject(s)
+ future: resolver.xml: for Norm Walsh's entity resolver submission, when done
+
+ src/ - root of Apache-defined Java code
+ src/org/apache/... etc
+
+ which.xml - Ant build file for org.apache.env.Which utility
+
c/ - root of all C/C++ related files
external/ - root of all externally-owned C/C++ sources
- apache/ - root of all apache-owned C/C++ sources
perl/ - root of all Perl related files
etc.
@@ -98,37 +153,68 @@ xml.apache.org subprojects to use the code that commons has. I.e. suggestions
and ways to package this code vis-a-vis the other project's code in a common way.
Other shared xml.apache.org guidelines? Like documentation format, testing techniques/policies, etc.
+