jvanzyl     2002/07/17 11:09:56

  Modified:    xdocs    naming-conventions.xml
  Log:
  o Adding a little more to the naming conventions, enough so that I can
    post to the list.
  
  Revision  Changes    Path
  1.2       +29 -3     jakarta-turbine-maven/xdocs/naming-conventions.xml
  
  Index: naming-conventions.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-turbine-maven/xdocs/naming-conventions.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- naming-conventions.xml    17 Jul 2002 16:50:58 -0000      1.1
  +++ naming-conventions.xml    17 Jul 2002 18:09:55 -0000      1.2
  @@ -108,11 +108,37 @@
           
           <p>
             <ul>
  -            <li>The project id is not used as the base name of the JAR</li>
  -            <li>The JAR name has no version declaration</li>
  +            <li>
  +              The project id is not used as the base name of the published
  +              JAR e.g. the Xerces products where xercesImpl is the base name
  +              of the published JAR. It neither matches the gump id or the 
  +              maven id.
  +            </li>
  +            <li>
  +              The published JAR name has no version declaration e.g. many of 
  +              the commons components do not declare a version as part of
  +              published JAR names.
  +            </li>
  +            <li>
  +              The project id is not used as the base name of the published JAR and
  +              the published JAR name has no version declaration e.g. the worst
  +              case scenerio which is the Java Activation Framework JAR which
  +              doesn't even vaguely follow other Sun naming conventions and there is 
no
  +              version declaration in the published JAR name. There isn't
  +              even any version information in the manifest.
  +            </li>
             </ul>
           </p>
  -
  +        
  +        <p>
  +          In most cases, any of these limitations can be overcome using the
  +          optional &lt;jar&gt; element or the JAR can be renamed. To date many
  +          of the Jakarta products have been renamed in the repository as it
  +          is likely in the near future that most Jakarta projects will choose
  +          to use Maven to build. But there isn't a firm policy about what to
  +          do in all cases which needs to be resolved.
  +        </p>
  +        
         </subsection>
       </section>
     </body>
  
  
  

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

Reply via email to