I tried your suggestion, but no luck.  I think I'm not including my classpath 
correctly in my build-junit-test.xml script.  I have ...

<project name="JUnitTests" default="run-all-tests" basedir=".">
  <import file="ant-common-checks.xml"/>
  <import file="build.xml"/>
  <property name="junitsrc" location="unittest"/>
  <property name="conf"  location="conf"/>
  <target name="build-tests" depends="check-junit">

and within "build.xml" I define what you suggest ...

  <path id="project.class.path">
        <fileset dir="${deployment}/APP-INF/lib/">
                <include name="*.jar"/>
        </fileset>
        <pathelement location="${weblogic-jar-path}"/>
        <pathelement location="${deployment}/APP-INF/lib/junit.jar"/>
  </path>

But how does my "" script understand to use the project.class.path as its 
classpath?

 - Dave


>  -------Original Message-------
>  From: Marc Weber <[EMAIL PROTECTED]>
>  Subject: Re: How to figure out what is in my class path?
>  Sent: Nov 24 '08 16:56
>  
>  On Mon, Nov 24, 2008 at 04:40:19PM +0000, [EMAIL PROTECTED] wrote:
>  > Hi,
>  >
>  > Is there a way to see what ANT thinks is in my classpath?  I have a 
> condition that's failing
>  >
>  >   <condition property="isJUnitAvailable">
>  >     <available classname="junit.framework.TestCase"/>
>  >   </condition>
>  >
>  >   <target name="check-junit" unless="isJUnitAvailable">
>  >     <fail message="Failed: JUnit not in classpath"/>
>  >   </target>
>  >
>  > But the JAR file (junit.jar) is set up in my project.class.path ...
>  >
>  >   <path id="project.class.path">
>  >         <fileset dir="${deployment}/APP-INF/lib/">
>  >                 <include name="*.jar"/>
>  >         </fileset>
>  >         <pathelement location="${weblogic-jar-path}"/>
>  >   </path>
>  >
>  > Not quite sure the right way to debug this.  Thanks, - Dave
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > For additional commands, e-mail: [EMAIL PROTECTED]
>  
>  That's a bug I've posted some days ago. The solution is to add the
>  classpath in the build.xml file manually after (after <path id="classpath">)
>      <pathelement location="${junit}/junit.jar"/>
>  
>  ${junit}/junit.jar is your junit.jar file
>  
>  sed command:
>  sed -i 's@<path id="classpath">@<path id="classpath"><pathelement 
> location="${junit}/junit.jar"/>@' build.xml
>  
>  
>  Hopefully someone with more knowledge about the ant build system can add
>  a one line fix so that this can be configured by -D or by
>  bulid.properties.
>  
>  If you want I can prepare a patch. Just tell me to do so.
>  
>  Anyway I wonder how ant devs do compile ant?
>  
>  Sincerly
>  Marc Weber
>  
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>  
>  

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

Reply via email to