cvs commit: spice/sandbox/repository/componenthaus todo.txt

hogie       03/11/05 11:35:49

  Modified:    sandbox/repository/componenthaus todo.txt
  Log:
  * Can have classes as service interfaces
   * Can have more than one service interface per submission
  
  Revision  Changes    Path
  1.10      +10 -4     spice/sandbox/repository/componenthaus/todo.txt
  
  Index: todo.txt
  ===================================================================
  RCS file: /cvsroot/spice/spice/sandbox/repository/componenthaus/todo.txt,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- todo.txt	3 Nov 2003 21:15:29 -0000	1.9
  +++ todo.txt	5 Nov 2003 19:35:49 -0000	1.10
  @@ -1,5 +1,5 @@
  - * take version number from maven pom
  - * take dependency jars from maven pom
  + * take version number from maven pom.  No, not the maven pom.  Let the user worry about how to get the version id to the Ant task.
  + * take dependency jars from maven pom. No, not the maven pom.  Let the user worry about how to get the author names to the Ant task.
    * Federation
    * Live XPath query/reporting of component model
    * Acceptable UI - gulp!
  @@ -7,16 +7,22 @@
    * Add Submit date to component
    * Access control (for write actions)
    * Users and user management
  - * Support multiple components in a single source tree (same jar I guess).
    * Rework the component details page.  Yes, link to impls, but display what a user has to do to use the impl
    * JMX integration into the heart of the app
    * Investigate Beanshell integration, for debugging problems while live
  - * Stop including plug-interfaces in the repository as public interfaces.  Allow the submitter decide whats public.
    * Fix search query - its only using the first word
    * Restarted prevayler is not loading objects correctly - all the string fields are "gone".
    * Disable multiple submissions of the same component.
  + * Structured API Search (Find me all methods taking a java.io.File and returning a java.lang.String, and importing java.sql classes)
  + * If the component is a class, show only its methods, to better convey the service offering.
  + * Consider providing a means of displaying test cases that use a particular service method.  Excellent way to convey purpose and usage of the service method.
   
   Done
  +
  +November 5th
  + * Stop including plug-interfaces in the repository as public interfaces.  Allow the submitter decide whats public.
  + * Support multiple components in a single source tree (same jar I guess).
  + * Allow the service interface to be a class (was limiting to interfaces up to this point, but thats too limiting)
   
   November 2nd
    * More test cases for search stuff
  
  
  


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/