[Nice-commit] Nice/src/nice/tools/ant Nicec.java,1.16,1.17

[<ag...@us...>]

Update of /cvsroot/nice/Nice/src/nice/tools/ant
In directory sc8-pr-cvs1:/tmp/cvs-serv11568/src/nice/tools/ant

Modified Files:
	Nicec.java 
Log Message:
Added comment and example on nested classpath usage

Index: Nicec.java
===================================================================
RCS file: /cvsroot/nice/Nice/src/nice/tools/ant/Nicec.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** Nicec.java	13 Mar 2003 16:38:21 -0000	1.16
--- Nicec.java	14 Mar 2003 12:37:42 -0000	1.17
***************
*** 86,94 ****
  			</tr>
  		</table>
  		<h3>Examples</h3>
! 		<pre>&lt;taskdef name=&quot;nicec&quot; classname=&quot;nice.tools.ant.Nicec&quot;/&gt;<br>
! 			&lt;target name=&quot;nice-compiler&quot;&gt;<br>
! 			  &lt;nicec package=&quot;test&quot; runtime=&quot;../share/java/nice.jar&quot;/&gt;<br>
! 			&lt;/target&gt;</pre>
  
  
--- 86,115 ----
  			</tr>
  		</table>
+ 
+ 		<h4>classpath</h4>
+ 		<p><code>Nicec</code>'s <i>classpath</i> attribute is a PATH like structure and can also be set via a nested
+ 		<i>classpath</i> element. This is very reasonable if you want to make your build script's pathes platform
+ 		independent. </p>
+ 		<h5>Example</h5>
+ <pre>  
+ 	&lt;nicec package=&quot;test&quot; &gt;
+ 	  &lt;classpath&gt;
+ 	    &lt;pathelement location=&quot;\test.jar&quot;/&gt;
+ 	    &lt;pathelement path=&quot;${java.class.path}&quot;/&gt;
+ 	  &lt;/classpath&gt;
+ 	&lt;/java&gt;
+ </pre>
+ 		<p>It is possible to use the <i>classpath</i> attribute together with the
+ 		<i>classpath<i> nested tag. In this case the result is a concatenated path.</p>
+ 		<p>It is highly recommended to use the nested version!<p>
+ 
+ 
  		<h3>Examples</h3>
! <pre>
! 	&lt;taskdef name=&quot;nicec&quot; classname=&quot;nice.tools.ant.Nicec&quot;/&gt;
! 	&lt;target name=&quot;nice-compiler&quot;&gt;
! 	  &lt;nicec package=&quot;test&quot; runtime=&quot;../share/java/nice.jar&quot;/&gt;
! 	&lt;/target&gt;
! </pre>