svn commit: r683629 - /maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt

[jv...@apache.org]

Author: jvanzyl
Date: Thu Aug  7 08:29:27 2008
New Revision: 683629

URL: http://svn.apache.org/viewvc?rev=683629&view=rev
Log:
some things to capture before going to list to ask for comments

Modified:
    maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt

Modified: maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt
URL: http://svn.apache.org/viewvc/maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt?rev=683629&r1=683628&r2=683629&view=diff
==============================================================================
--- maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt (original)
+++ maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt Thu Aug  7 08:29:27 2008
@@ -1,11 +1,14 @@
 h1. Maven 2.1 -- Jason van Zyl
 
-- architecture document for maven-shared-model and the new project building code
-- architecture document and spec for mercury (largely in the wiki)
-- architecture document on maven itself
- - plugin manager
- - lifecycle executor
-- profile construction
+TODO: Jesse and Greg spent a lot of time getting the async SSL working so a little description this work would be useful
+TODO: architecture document about Mercury transport as the async HTTP/DAV client
+TODO: architecture document for maven-shared-model and the new project building code
+TODO: architecture document and spec for mercury (largely in the wiki)
+TODO: architecture document on maven itself, plugin manager, lifecycle executor, profile construction
+TODO: check with kenney to see if his work survived in substituting components or if it's his work that's actually making it work
+TODO: get an explanation of the process Arnaud and Benjamin have for plugins. I started by capturing the log
+TODO: document standard setup for Hudson we have so people can see the results of testing
+TODO: setup hudson with emma for code coverage and ask VELO to help us setup coverage for integration tests
 
 h2. Architectural Goals
 
@@ -100,7 +103,6 @@
 [08:18am] jason: and any discussion about compatibility is pointless until that's done
 {code}
 
-
 h3. POM changes
 
 There are many changes that users have requested in the POM, in addition to wholesale formatting changes. Acommodating these requests is a little tricky