I'm running Ant 1.6.  Since I'm not the sysadmin, I can't easily upgrade.  

I've tried the "-lib" directive in my shell script ...

ant -lib 
/export/third-party/etsbea/staging/wls_9.2.2/CedarPoint_Service/deployment/APP-INF/lib/junit.jar
  -buildfile build-junit-test.xml -Denv=$WLS_ENV -Dtier=$TIER 
-Dwlshosturl=$hosturl -Dwlsuser=$username -Dwlspwd=$password -Dpwd=$pwd $target

but my condition is still failing.  Does anyone know a smaller test I can run 
to troubleshoot this problem further?

Thanks, - Dave



>  -------Original Message-------
>  From: Peter Reilly <[EMAIL PROTECTED]>
>  Subject: Re: How to figure out what is in my class path?
>  Sent: Nov 24 '08 22:03
>  
>  With current ant tasks, one cannot change the classpath used within 
> build.xml.
>  
>  For junit and ant 1.7.0 +, one can set the location of the junit.jar
>  file within the <junit>
>  task itself - this is indeed the recommended way as it means that one
>  does not need to modify the ant distribution or use -lib at the command line.
>  
>  
>  <junit ...>
>     <classpath>
>          <path refid="location junit.jar"/>
>         ....
>     </classpath>
>  </junit>
>  
>  Peter
>  
>  
>  On Mon, Nov 24, 2008 at 4:40 PM,  <[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]
>  >
>  >
>  
>  ---------------------------------------------------------------------
>  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