jvanzyl     2002/07/15 20:57:52

  Modified:    xdocs/ref musings.xml
  Log:
  o removing some entries as they have actually been implemented
  
  Revision  Changes    Path
  1.5       +1 -33     jakarta-turbine-maven/xdocs/ref/musings.xml
  
  Index: musings.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-maven/xdocs/ref/musings.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- musings.xml       28 May 2002 09:56:52 -0000      1.4
  +++ musings.xml       16 Jul 2002 03:57:51 -0000      1.5
  @@ -64,12 +64,6 @@
             eventually.
          </li>
          <li>
  -         Figure the scenario where the project must generate sources before
  -         building. We have some crappy deps in the fulcrum build that need
  -         to be cleaned up. The dependencies between the targets need to
  -         be well defined and documented.
  -       </li>
  -       <li>
            The use of profiles for testing like we have in the tdk and torque.
            How they can be made to work easily for developers working in
            different environments. We also want to be able use multiple
  @@ -81,12 +75,6 @@
            of profiles looking for problems.
          </li>
          <li>
  -         Must account for a difference between the login name on the machine
  -         the user is working and where the site and distributions are
  -         being deployed. Maybe some values in build.properties. Martin
  -         can't currently deploy the site because of this.
  -       </li>
  -       <li>
            Integrate a simple link checker for the generated site so that
            it is internally consistent.
          </li>
  @@ -163,19 +151,6 @@
            browsers, PDF for printed materials).
          </li>
          <li>
  -         Do we need to abstract out Ant so that projects can be built with
  -         any tool.
  -       </li>
  -       <li>
  -         Do we need to abstract out CVS so that any repository can work.
  -         Probably because subversion is on its way and will more than
  -         likely be ready soon and we want to take advantage of that.
  -       </li>
  -       <li>
  -         How to integrate @todo items that are listed in the source with
  -         todos that are unrelated to currently existing source files.
  -       </li>
  -       <li>
            A common format for project usecases. Scarab has made a start here so that
            would be good to integrate.
          </li>
  @@ -184,7 +159,7 @@
            provided by the Unified Software Development Process.
          </li>
          <li>
  -         How to easy link to references. The same mechanism that is used to
  +         How to easily link to references. The same mechanism that is used to
            link entries in the glossary can be used.
          </li>
          <li>
  @@ -192,13 +167,6 @@
            services, for Torque this might be a registry of ID generation
            strategies. But cataloging these entries easily and having
            them be indexed.
  -       </li>
  -       <li>
  -         How to run the update-jars target auto-magically, comparison
  -         of timestamps periodically ... don't know yet. We probably don't
  -         want to run the update-jars target every time we build. A user
  -         may not be online and it would probably get annoying if it
  -         went off all the time.
          </li>
          <li>
            Automate announcements to the big sites.
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to