dion        2002/06/03 08:37:55

  Modified:    xdocs    tasks.xml
  Log:
  Added plugin discussion items
  
  Revision  Changes    Path
  1.22      +32 -0     jakarta-turbine-maven/xdocs/tasks.xml
  
  Index: tasks.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-maven/xdocs/tasks.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- tasks.xml 1 Jun 2002 21:55:35 -0000       1.21
  +++ tasks.xml 3 Jun 2002 15:37:55 -0000       1.22
  @@ -57,6 +57,38 @@
               <li>
                 Look at release guide in tomcat 4.
               </li>
  +            <li>
  +              Add maven:plugin-list target to list all known plugins from
  +              remote repos. Each repo may optionally provide a plugins.list
  +              file similar to the jars.list. A plugin is packaged as a jar file.
  +            </li>
  +            <li>
  +              Add maven:plugin-install which looks for a property, <code>
  +              maven.plugin.name</code> for a plugin (minus the .jar) to find in
  +              a remote repo, download into <code>${maven.home}/plugins</code>
  +              and unjar into <code>${maven.home}/plugins/${maven.plugin.name}</code>
  +            </li>
  +            <li>
  +              Add a maven:plugin-delegators which produces a 'delegator list'
  +              to be included into a build.xml file. The list is obtained by
  +              scanning installed plugins, and reading their <code>plugin.xml</code>
  +              document for <code>target</code> or <code>exports</code>. A target
  +              is an entry point into the plugin, e.g. 
<code>maven:validate-war</code>.
  +              An <code>export</code> is an entry added into an existing <code>
  +              target</code>, e.g. a plugin might add the <code>maven:docs-latex
  +              </code> into the <code>maven:docs</code> target before usual 
  +              maven:docs processing is invoked. So exports can be before or 
  +              after.
  +            </li>
  +            <li>
  +              plugin.xml may also list other plugins that the plugin is 
  +              dependent on, which must be downloaded and installed as well.
  +            </li>
  +            <li>
  +              All plugins must provide intense sizzle, be goal-oriented, cooperate 
  +              in a plug &amp; play manner, and optionally provide a powerpoint
  +              presentation describing their management potential.
  +            </li>
             </ul>
           </p>
         </subsection>
  
  
  

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

Reply via email to