BTW, the slide block can compile with the help of the mock classes, but doesn't working without a copy of jta.jar, similar to the mail example.
So, should we really remove the warning? Stephan Michels. On 7 Feb 2003 [EMAIL PROTECTED] wrote: > cziegeler 2003/02/07 05:17:15 > > Modified: . build.xml > Log: > Removing warning for transaction (which is not used) > > Revision Changes Path > 1.319 +2 -17 xml-cocoon2/build.xml > > Index: build.xml > =================================================================== > RCS file: /home/cvs/xml-cocoon2/build.xml,v > retrieving revision 1.318 > retrieving revision 1.319 > diff -u -r1.318 -r1.319 > --- build.xml 5 Feb 2003 13:33:47 -0000 1.318 > +++ build.xml 7 Feb 2003 13:17:14 -0000 1.319 > @@ -529,10 +529,6 @@ > classname="javax.activation.DataSource"/> > > <available classpathref="classpath" > - property="transaction.present" > - classname="javax.transaction.Transaction"/> > - > - <available classpathref="classpath" > property="mail.present" > classname="javax.mail.message"/> > </target> > @@ -812,17 +808,6 @@ > </antcall> > </target> > > - <!-- Outputs a warning if javax.transaction.* classes are missing during >compilation --> > - <target name="transaction-warn" unless="transaction.present" >depends="optional-tests"> > - <antcall target="op-warning"> > - <param name="thing" value="Transaction"/> > - <param name="recovery" > - value="Get the SUN Java Transaction package and place the jar in the >lib/local dir"/> > - <param name="message" > - value="The SUN Java Transaction package is required for the Slide >classes"/> > - </antcall> > - </target> > - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
