jvanzyl     2002/11/24 21:45:31

  Modified:    src/java/org/apache/maven/app Maven.java
  Log:
  o removing completed todo.
  
  Revision  Changes    Path
  1.142     +2 -10     jakarta-turbine-maven/src/java/org/apache/maven/app/Maven.java
  
  Index: Maven.java
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-maven/src/java/org/apache/maven/app/Maven.java,v
  retrieving revision 1.141
  retrieving revision 1.142
  diff -u -r1.141 -r1.142
  --- Maven.java        24 Nov 2002 20:55:14 -0000      1.141
  +++ Maven.java        25 Nov 2002 05:45:31 -0000      1.142
  @@ -98,20 +98,12 @@
    * @version $Id$
    *
    * @todo Filter the Maven version number into a Java constant that will change
  - *       during compilation
  + *       during compilation.
    * @todo Remove any notions of the filesystem. This should strictly be
    *       a logical entity for building projects.
    * @todo Maven should be given an live instance of a Project object. Any
    *       logic like checking for the existance of a project.xml file and
    *       it's size should be moved to the CLI wrapper.
  - * @todo Maven should be given a live MavenJellyContext that is fully
  - *       populated according to rules stated by the wrapper. For example,
  - *       it is a rule of CLI invocation that properties are loaded in
  - *       a certain way. Other wrappers may (but most likely not) do things
  - *       differently. The properties merging or overriding should take
  - *       place in a utility class to provide default operations. As such
  - *       the properties handling will be moved out of this class and
  - *       left to the CLI wrapper.
    * @todo Use the context to pass information into Maven. We will consider
    *       Maven a component and pass the information into Maven using a
    *       context a la Avalon.
  
  
  

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

Reply via email to