ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-ant/docs ant_task_guidelines.html
Date Thu, 09 May 2002 17:42:37 GMT
stevel      02/05/09 10:42:37

  Modified:    docs     Tag: ANT_15_BRANCH ant_task_guidelines.html
  stuff on letting ant set your attributes, on account of having looked at the Apache Axis
  Revision  Changes    Path
  No                   revision
  No                   revision   +13 -5     jakarta-ant/docs/ant_task_guidelines.html
  Index: ant_task_guidelines.html
  RCS file: /home/cvs/jakarta-ant/docs/ant_task_guidelines.html,v
  retrieving revision
  retrieving revision
  diff -u -r1.5.2.2 -r1.5.2.3
  --- ant_task_guidelines.html	7 May 2002 10:50:17 -0000
  +++ ant_task_guidelines.html	9 May 2002 17:42:37 -0000
  @@ -80,13 +80,21 @@
   One important rule is 'no tabs'. Use four spaces instead. Not two,
   not eight, four. Even if your editor is configured to have a tab of four
   spaces, lots of others aren't -spaces have more consistency across
  -editors and platforms.
  +editors and platforms. Some IDEs (JEdit) can highlight tabs, to stop you
  +accidentally inserting them
  -<h2>Recommended Names for attributes and elements</h2>
  +<h2>Attributes and elements</h2>
  +Use the Ant introspection based mapping of attributes into Java datatypes,
  +rather than implementing all your attributes as setFoo(String) and doing
  +the mapping to Int, bool or file yourself. This saves work on your part,
  +lets Java callers use you in a typesafe manner, and will let the Xdocs 
  +documentation generator work out what the parameters are.   
   The ant1.x tasks are very inconsistent regarding naming of attributes
  --some tasks use source, others src. Here is a list of preferred attribute
  +-some tasks use <tt>source<tt>, others <tt>src</tt>tt>. 
  +Here is a list of preferred attribute names. 
  @@ -193,7 +201,7 @@
   <tt>assert</tt> keyword, which is only enabled if the compiler is told
   to compile 1.4 version source. Clearly with the 1.1 compatibility requirement,
   Ant tasks can not use this keyword. They also need to move away from
  -using the JUnit <tt>assert()</tt> method and start calling <tt>assertTrue()</tt>
  +using the JUnit <tt>assert()</tt> method and call <tt>assertTrue()</tt>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message